coc-ccls VS coc-diagnostic

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:

As recommended by michaelsbradley below, I installed https://github.com/nim-lang/langserver. I'm using coc.nvim (https://github.com/neoclide/coc.nvim) so I followed the instructions here from nim langserver https://github.com/nim-lang/langserver#vimneovim and seems to be working well!

Actually, I'm maintaining coc-perl (https://github.com/bmeneg/coc-perl), which enables the use of Perl LSP extension for vcode on vim/neovim using the CoC (https://github.com/neoclide/coc.nvim) backend. But it's completely on top of Perl::LanguageServer.

For vim specifically, I've been using coc.nvim, which works pretty well for my needs, and I know its quite popular. Another fairly popular one is YouCompleteMe, which I had taken a look at for some other languages; but ended up just using coc as I can't justify using YCM once a year (if that) -- too much "headache" for not a lot of use, you know?

Plug 'https://github.com/neoclide/coc.nvim' " Auto Completion

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Sounds like you want vim-which-key and coc.nvim.

Another option is to just download https://github.com/neoclide/coc.nvim Which is basically a one stop shop for completion, and it's pretty fast, it just uses nodejs instead of built in nvim lua functions.

coc.nvim

dont over copy and paste example .vimrc, keep it simple and grow tooling as you use. for linting and code completion : https://github.com/neoclide/coc.nvim (easy to add languages)

More specifically, i use coc-diagnostic extension , with the default configuration for python linting as advised in coc-jedi-lint repo .

I'm currently using vim + coc + coc-diagnostic + rust-analyzer for all my Rust dev work. Clippy is very helpful and I'd like to configure Vim to give me inline suggestions from Clippy.

Full list here. Since the tool is a linter, it sounds like it should work with language servers. I use CoC.nvim for LSP features. Thankfully some smart guys have figured out how to make proselint work with coc.nvim & coc-diagnostic (see here). Now it works for my blog posts just like clangd does for my C++ code.