rust.vim VS coc.nvim

I am using rustaceanvim and rust.vim.

When the file first loads, it uses the syntax defined in the $VIMRUNTIME/syntax/rust.vim file from rust.vim, which is what I want, but after a few seconds (probably once rust-analyzer loads and runs), it changes the highlighting to use different colours (there's probably a better way to describe it, but a video is easier to show). This colour change also happens when I write the file (and rust-analyzer runs again).

Or this https://github.com/rust-lang/rust.vim, it has example with running tests

If you need basic syntax checking on leaving insert mode (without saving file), https://github.com/rust-lang/rust.vim can be used

Seems like there's a tree-sitter solution, but I do want to note that this works out of the box with rust.vim: https://github.com/rust-lang/rust.vim/issues/63. It might be the built-in Rust support is out of date -- using that repo as a plugin would do the trick.

Most of the customizations in the $VIMRUNTIME's rust ftplugin are guarded behind a flag (g:rust_fold, g:rustfmt_autosave,g:rust_recommended_style, etc.) to control enabling and disabling them, but for some reason the navigation mappings are unconditionally defined, with no flag to turn them off... It might be worth going through the issues in https://github.com/rust-lang/rust.vim to see if that ever came up before.

Is having rust.vim necessary if I'm using rust-tools already?

Primeagen has a series, you could also try spacevim or lunarvim( i prefer lunarvim). If you want to read the docs and setup yourself 1. lsp and code completion mentioned in #5. 2. treesitter 3. lsp handles that, you have to install java's lsp, this improves its look. 4. Make your own remaps, some languages have a plugin for this but i can't find one for java, this is the one for rust. 5. Install cmp and one of the snippet engines.

writing rust is the same regardless of which editor you use and using vim is the same regardless of what programming language you are in, so i dont think you need a tutorial neccissarily. ive been using this plugin for rust-specific features https://github.com/rust-lang/rust.vim

As for plugins for Rust development, I’d recommend Conquer of Completion (using the coc-rust-analyser coc plugin), Rust lang’s rust plugin, and the Toml plugin

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