vim-grepper VS ripgrep

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?

ripgrep - https://github.com/BurntSushi/ripgrep

Basic code searching skills seems like something new developers are never explicitly taught, but which is an absolutely crucial skill to build early on.

I guess the knowledge progression I would recommend would look something kind this:

- Learning about Ctrl+F, which works basically everywhere.

- Transitioning to ripgrep https://github.com/BurntSushi/ripgrep - I wouldn't even call this optional, it's truly an incredible and very discoverable tool. Requires keeping a terminal open, but that's a good thing for a newbie!

- Optional, but highly recommended: Learning one of the powerhouse command line editors. Teenage me recommended Emacs; current me recommends vanilla vim, purely because some flavor of it is installed almost everywhere. This is so that you can grep around and edit in the same window.

- In the same vein, moving back from ripgrep and learning about good old fashioned grep, with a few flags rg uses by default: `grep -r` for recursive search, `grep -ri` for case insensitive recursive search, and `grep -ril` for case insensitive recursive "just show me which files this string is found in" search. Some others too, season to taste.

- Finally hitting the wall with what ripgrep can do for you and switching to an actual indexed, dedicated code search tool.

live grep: ripgrep

The world has moved on though to opinionated tools, and Rust isn't even the furthest in that direction (That would be Go). The equivalent of those two lines in Cargo.toml would be this example of a basic configuration from the jacoco-maven-plugin: https://www.jacoco.org/jacoco/trunk/doc/examples/build/pom.x... - That's 40 lines in the section to do the "defaults".

Yes, you could add a load of config for files to include/exclude from coverage and so on, but the idea that that's a norm is way more common in Java projects than other languages. Like here's some example Cargo.toml files from complicated Rust projects:

Servo: https://github.com/servo/servo/blob/main/Cargo.toml

rust-gdext: https://github.com/godot-rust/gdext/blob/master/godot-core/C...

ripgrep: https://github.com/BurntSushi/ripgrep/blob/master/Cargo.toml

socketio: https://github.com/1c3t3a/rust-socketio/blob/main/socketio/C...

I'm not clear on why you're seeing the results you are. It could be because your haystack is so small that you're mostly just measuring noise. ripgrep 14 did introduce some optimizations in workloads like this by reducing match overhead, but I don't think it's anything huge in this case. (And I just tried ripgrep 13 on the same commands above and the timings are similar if a tiny bit slower.)

[1]: https://github.com/radare/ired

[2]: https://github.com/BurntSushi/ripgrep/discussions/2597

Explore o Ripgrep no repositório oficial: https://github.com/BurntSushi/ripgrep

🔎🗃️ ripgrep or ugrep (search fast, use regex patterns or fuzzy search, pipe output to bash/zsh shell for further processing V coloring)