NrrwRgn

I lean a fair bit in the opposite direction. If a sort is any more complex than -n or -k<number no flags>, I tend to vipe¹ my sort in my editor. It feels great when you can use narrow-to-region² to perfect a complex address or write a custom function with all your editor's power at your fingertips. With the sad, but obvious, drawback that the changes aren't linked in your disjoint shell and editor history. ¹ https://manpages.debian.org/jessie/moreutils/vipe.1.en.html ² Nowadays, that is more likely https://github.com/chrisbra/NrrwRgn for me.

On a more general level, Christian Brabandt's re-imagining of emacs' region narrowing can be a great work to work files that contain complex embedded strings. Much like the emacs feature it is useful outside this specific use case too, and it can be a great way to perform heavy edits without needing to care about boundaries and such. ¹ https://github.com/chrisbra/NrrwRgn

I have been using NrrwRgn[0] for editing and presenting individual sections of code. How does Yode compare? [0]: https://github.com/chrisbra/NrrwRgn

> I hit :w so reflexively and regularly in working files that swap files only occasionally saves my butt I'm definitely one of those people too, and while I don't disable swap files I do depend heavily on `persistent-undo`. It literally changed the way I work when it was introduced. To some extent I treat it as an extension to swapfile functionality as it also operates across broken sessions(intentional or not). > [...] the user experience with them Christian Brabandt's Recover.vim¹ is a huge improvement for those few times when you do actually want to work with a swap file. General recommendation to poke around in his other repositories too, as he has written a heap of extremely useful vim things. Edit: Especially unicode.vim² which improves `ga` no end, csv.vim³ which feels like magic, NrrwRgn⁴ for fellow emacs refugees, and ... ¹ ht