coc.nvim VS nerdtree

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

I personally use nerdtree. Add nerdtree-git-plugin too, that's nice when looking at your project (for files, use vim-gitgutter).

nerdtree is another very popular option

Using my toy js refactoring plugin and NERDTree.

2) Syntax check https://github.com/vim-syntastic/syntastic 3) File navigation https://github.com/preservim/nerdtree 4) Autocomplete There are many autocomplete extensions. I haven't found one that I feel comfortable to recommend. Another way is to create a txt file with all the key words and lines in the languages you use, make an autocommand that adds the txt file to the buffer, and then use ctrl-n or ctrl-p to autocomplete. You can also use ctrl-x-ctrl-l to autocmplete entire lines. 5) Running code Add commands in your .vmrc to run the current file as a a whatever file. I use :J to run java files, :P to run python files, :C to run c files and so on. For example, this is my command to run a java file: command J execute "!java %:t"

Plug 'https://github.com/preservim/nerdtree'

My basic vim workflow is that I open vim, which opens NerdTree for me by default. I can find the file I want in NerdTree, or I can hit Ctrl+p to open a file with fuzzy searching.

What's also useful is to have a tree plugin (such as nvim-tree or nerdtree), so you can just open any file in the workspace (or outside it) if needed. That way, even if you delete a buffer, you can just come back to a file whose buffer you deleted.

Worth noting Nerdtree’s repo is now at https://github.com/preservim/nerdtree and not at https://github.com/scrooloose/nerdtree