Fast by default, and quiet about what it skipped.
Most ripgrep confusion is not a bad regex — it's a file that never got opened.
Why ripgrep "missed" your file
Before ripgrep reads a single byte, four gates decide whether a file is even opened.
Each gate has the flag that opens it. Hover a gate to read what it drops; click it to filter
the flag list below.
Hover a band to read what it drops. Click it to filter the flags below.
From pattern to output
Once a file is open, two more decisions shape what you see: which regex engine runs, and what
ripgrep prints when it hits. Click any box to filter the flags below.
Hover a box to read what it changes. Click it to filter the flags below.
Every flag, filtered
Search by flag, command, or what you want to do. Click any card to copy it.
The twenty flags
The ones worth holding in your head. The four in cyan are the everyday defaults —
put --smart-case in your config and you can stop typing one of them.