6 ms·
Sounds like the problem you have here is that `grep` is aliased to `ripgrep`. ripgrep isn't intended to be a drop-in replacement for POSIX grep, and the subject
by exdeejay_ 11mo ago
Sounds like the problem you have here is that `grep` is aliased to `ripgrep`. ripgrep isn't intended to be a drop-in replacement for POSIX grep, and the subjectively easier usage of ripgrep can never replace grep's matureness and adoption.
Note: if you want to make ripgrep not do .gitignore filtering, set `RIPGREP_CONFIG_PATH` to point to a config file that contains `-uu`.
Sources:
- https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#configuration-file https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#c...
- https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#automatic-filtering https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md#a...
- BrouteMinou 11mo agoSo I stand corrected. I did indeed use ripgrep as a drop-in replacement. That's on me!
- great_wubwub 11mo agoI've been playing around with this over the years and this is what I put in my .rgrc: --smart-case --no-messages --hidden --ignore-vcs and then point to it with .zshenv 3:export RIPGREP_CONFIG_PATH="$HOME/.rgrc" Not perfect and sometimes I reach for good old fashioned escaped \grep but most of the time it's fine.