That’s a fabulously well-written article: very insightful and demonstrating remarkable self-awareness. It inspired me to check out the README for ripgrep and I was equally impressed with the quality of its documentation.
Until now, I’ve always shied away from any of the modern `grep`-like programs as I prefer to be comfortable with the standardised utilities as specified by POSIX (`find` and `grep`). However, I often find myself using GNU extensions – since they’re so useful and make certain tasks easier. I figured today would be a good day to take it a step further and try out `ripgrep`. One feature that immediately appeals to me is that `rg` automatically respects `.gitignore` and skips hidden files/directories and binary files; When searching recursively, I pretty much always use `-I` with GNU grep and often use its `--exclude` and `--exclude-dir` options (features not specified by POSIX). I’m looking forward to experimenting with ripgrep and discovering what other benefits it can offer.
Until now, I’ve always shied away from any of the modern `grep`-like programs as I prefer to be comfortable with the standardised utilities as specified by POSIX (`find` and `grep`). However, I often find myself using GNU extensions – since they’re so useful and make certain tasks easier. I figured today would be a good day to take it a step further and try out `ripgrep`. One feature that immediately appeals to me is that `rg` automatically respects `.gitignore` and skips hidden files/directories and binary files; When searching recursively, I pretty much always use `-I` with GNU grep and often use its `--exclude` and `--exclude-dir` options (features not specified by POSIX). I’m looking forward to experimenting with ripgrep and discovering what other benefits it can offer.
So thanks, Burntsushi/Andrew.