NrrwRgn VS vim-sleuth

Throwback to a real classic: narrow region

I lean a fair bit in the opposite direction. If a sort is any more complex than -n or -k, 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.

NrrwRgn ?

chrisbra/NrrwRgn - Opens focussed part "region" of the buffer

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

Wow! It's like https://github.com/chrisbra/NrrwRgn with steroids! Good job!

https://github.com/chrisbra/NrrwRgn might work. Narrow the region to that of only the script and change the filetype (:set filetype=typescript) of the narrowed regions buffer (it will open a separate window, with its own buffer) to that of the server you want and then do :Lsp start. Haven't tried it myself as I do not write any html with embedded script.

My use case is somewhat similiar to https://github.com/chrisbra/NrrwRgn and maybe i could tweak it to actually do it, but i feel it's not quite there. I'd like to still se the other regions of the code while editing.

In addition to setting tabstop and shiftwidth, you might also like this plugin: https://github.com/tpope/vim-sleuth

vim-sleuth auto detects tab size so...

Just add https://github.com/tpope/vim-sleuth and never worry about it again.

At the end of the day I don't really care which a project goes with, I've always just used vim-sleuth to automatically set my tab key to input whatever the current file's indentation is.

VsCode has an internal function from auto-detecting indentation, while my config uses vim-sleuth with indent-blankline.nvim.

If you work a lot on legacy codebases, https://github.com/tpope/vim-sleuth is probably more what you need than editorconfig, as it will work even when one is not present.

The primary advantage of using it is that it has built in heuristics for detecting line wrapping when opening a file (with some Treesitter magic for Markdown to make it more accurate), and also allows for manual swapping between wrapping types. You can think of it as the wrapping equivalent to vim-sleuth.

I just found about Tim Pope's sleuth: https://github.com/tpope/vim-sleuth It supports editorconfig but it also seems to have just better heuristics when an editorconfig file isn't present, so I just decided to replace `editorconfig-vim` with it.

Another solution is try sleuth.vim, that sets automatically your indentation based on the project, buffer and editorconfig