Agreed. My most common use case for "finding stuff" on linux boxes is me looking for particular strings in clear text files, so I often end up doing "grep string -Ri {/etc,/var} | less".
Also, though find seems to be POSIX compliant, I just don't like it's syntax and how flags are handled.
Re:An intro to finding things in Linux
by npteljes on Tuesday November 23, 2021 @10:22AM
(#29318823)
For that I like to install ripgrep or `rg` for short, very nice defaults and formats the output nicely too.
Installing the tools you prefer is not always an option, but I agree, ripgrep is great.
Re:An intro to finding things in Linux
by alex_smart on Saturday November 27, 2021 @11:39AM
(#29361380)
You can always put some binaries in $HOME/bin.
You cannot "always" do this because some of us frequently or occasionally work in environments where external, non-reviewed software simply isn't allowed.
`fd` seems pretty useful, but I tend to just `find . -name '*whatevs*'`. It's a bit longer, but one less tool to make sure you have available (and find is everywhere), and one less tool to learn. Even just `find . | grep whatevs` is fine.
Re:An intro to finding things in Linux
by gpderetta on Tuesday November 23, 2021 @09:28AM
(#29318182)
I never bothered to learn all the find options, so find|grep is also my usual goto.
Re:An intro to finding things in Linux
by norvvryo on Tuesday November 23, 2021 @09:43AM
(#29318334)
POSIX find is a lot less daunting than GNU if you're looking for somewhere to start.
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/f...
I am sure that well-versed users can achieve wonderful things with it; myself, I either use fd or pipe "du -a" into grep (or rg), and move on with my life.