Best suited to repeatable local searches
ripgrep, invoked as rg, is a command-line search tool available for Windows, macOS and Linux. It searches directory trees and supports regular expressions. Its main appeal is a concise, repeatable search that stays close to local project files. Developers, technical writers and maintainers working across many text files are a natural audience. This review evaluates documented behaviour; it does not claim independent speed measurements.
Begin with a literal search
Try rg -n -F payment_status src in a project that has a src directory. The fixed-string option treats the search text literally, while line numbers make matches easier to locate. Use rg -l -F payment_status src when you only need matching filenames. These commands are examples: replace both the search term and the directory. Start with one known match so that you can confirm the search covers the intended files.
Understand why files may be absent
Default filtering respects ignore rules and skips hidden and binary files. That often reduces distracting results, but it also means a missing match is not proof that the text does not exist anywhere. Use rg --files to inspect the normal file inventory, then adjust the search scope deliberately. Include hidden or ignored files only when the task requires them. Avoid confusing a directory-selection problem with a pattern problem.
Use regular expressions deliberately
Literal search is the clearer choice for exact identifiers and punctuation. Use regular expressions when you need a pattern, and test them against a short example first. The default engine does not support every advanced regex feature; PCRE2 support, when included in the build, is available through the -P option. Scripts intended for other machines should state their requirements instead of assuming identical tool builds.
Our editorial recommendation
Adopt ripgrep for repeated searches across local text projects, especially when a saved command helps colleagues reproduce the task. Keep a browser text tool for small pasted snippets or quick transformations. Before adding a search to automation, verify expected matches, filenames and exit handling on representative input. Measure your own workload if speed matters. Useful defaults and reproducible commands are stronger reasons to adopt a tool than an unverified headline speed ratio.
github.com