vim-grepper VS coc.nvim

I'm curious, what specifically works better about their IDE for you in the case of many files? Do they now have good global refactoring tools, like you can change a class name in library A and have it automatically be updated in library B and application C that depend on and use it? And without the actual files for such being open? (I'm reduced to what's essentially mass search-replace with https://github.com/mhinz/vim-grepper/ but it does the job and importantly helps update files I might not have open buffers for. Still a step down from what's available in JavaLand. I remember someone was working on a library to build some modern refactoring tools for Lisp but I don't know how far that's gotten.)

J'aime bien https://github.com/mhinz/vim-grepper Et https://github.com/kevinhwang91/nvim-bqf Pour ce travail.

I had a look at your planned modules and thought I could swamp you with some more ideas, to possibly inspire you to do a few of them: - since you are thinking about making mini.quickfix: - vim-grepper: eases configuration of grep tools like rg and integration with quickfix - recipe.nvim: instead of defining 'makeprg', making a build step, which can send errors to the quickfix and a run step which runs in a floating terminal - qf.nvim: adds some additional stuff to quickfix, on top of bqf, like a proper quickfix toggle command, which I never want to live without again

use a grep tool plugin, I like https://github.com/mhinz/vim-grepper for this.

This is great when you want to jump to a specific place.

I also use vim-grepper (mapped to leader-g) for finding in files and populating the quickfix list.

https://github.com/mhinz/vim-grepper

Why not just using vim-grepper? :p

Not an answer to your question but vim-grepper allows you to use ag already (if you are using it from grepping).

This wouldn’t be a direct replacement for searching, but could you create/find a tool which uses perl regex to fill the location window? e.g you can use vim-grepper and modify the rg command with --pcre to use the pcre2 engine.

Could you expand on how this differs from vim-grepper?

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