lh-vim-lib VS coc.nvim

and it seems it depends now on lh-vim-lib (to be able to set dictionaries: :let b:dict.key.subkey.whatever = 42: https://github.com/LucHermitte/lh-vim-lib (install it with your plugin manager)

Note that if it's just for setting a few standard options, editorconfig will be enough for most of us. It won't work if you want to define different mappings, or if you want to change the path to your snippets (actually editorconfig plugin could be hijacked to set vim variables)

here an UI alternative to confirm() and another that implement comboboxes: https://github.com/LucHermitte/lh-vim-lib/blob/master/autoload/lh/ui.vim (the code is very old, but it works search for getchar())

Regarding project management, .exrc is enough as long we're working on simple project where everything is in the same directory. On real project I've ended up needing and writing much, much more.

or in your .editorconfig file (if you have any) as lh-vim-lib also registers an extension to set vim variables from editorconfig file -- it's definitively not meant to be used this way, but well it's possible.

I have things on the same topic in my vimscript library: I provide a queue object into which I register related tasks that cannot be safely parallelized.

As well as its own plugins Vim/NeoVim can use VSCode's LSPs, DAPs and extensions either directly or via plugins like CoC[1] and Mason[2].

I would be surprised if emacs couldn't do the same.

1. https://github.com/neoclide/coc.nvim

The most famous TypeScript one probably is coc.nvim

It is flatly the wrong mindset to think of vim as an IDE. vim is a code editor: get in, make change, get out. Consider vim koans, which are a fun little read. You can throw coc.nvim at Neovim, along with a few other bits to give you a Good Enough setup, but vim isn't and will never be an IDE.

I just did a fresh reinstall of CoC, on a newer version of Neovim. I'm now seeing something I hadn't seen before, which CoC calls "inlay hints". They look like this:

I'm currently on an old setup (using coc and polyglot) and nvim v0.6.1. I'll be updating to a more modern setup within next year, using the native lsp and building nvim more frequently. But that's not today.

coc.nvim

There are some plugins which have the best documentations I have ever seen, but you need to read it from the Vim.

Example of coc.nvim: https://github.com/neoclide/coc.nvim/blob/master/doc/coc.txt

Actually you can with coc.nvim & coc-sh. So long as shellcheck is also installed and in PATH, it'll integrate with coc/vim just fine.

When you install an extension it runs an npm install or yarn, iirc, which is going to be problematic for you being offline. I was going to say you could copy that ~/.config/coc folder directly to the other machine but yeah, Windows, no idea. You see here https://github.com/neoclide/coc.nvim/wiki/Using-coc-extensions

You can try https://github.com/neoclide/coc.nvim, the pre-requisite is to install nodeJS, then to install all the languages LSP. This works for me for Angular, Rust, JavaScript, Vimscript, etc