vim-rooter VS vim-grepper

This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.

maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim

The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:

It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.

An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter

I just use rooter and avoid thinking about it...

There's vim-rooter, which is great.

No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.

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?