idiomatic-vimrc VS coc.nvim

Now a days my vimrc is less than 150 lines, and using Vim is good again. This helped me a lot: https://github.com/romainl/idiomatic-vimrc

Learning basic movement in vim can take about an hour or more, but setting up your own custom configuration that you are happy with can a month or longer (unless you use a preconfigured vimrc, but then you run into the issue of not understanding how to fix things if they break or not being able to add configuration to scratch your own niche itches). If you have time, and enjoy customization then go for it. Heres some basic guidelines for making your vimrc https://github.com/romainl/idiomatic-vimrc

idiomatic vimrc by romainl

My suggstion is do whatever you want. It's your config, not ours. Just know that if you stick to vim you'll eventually realize that your own personal workflow likely wont require a lot of plugins. I found https://github.com/romainl/idiomatic-vimrc useful as a reference when crafting my own config. I think it's a solid write-up.

I also recommend you use nearly blank vimrc. You should roughly understand each line in your vimrc. Use :help and google learn more.

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