Ripgrep 15.0

Post by burntsushi » Sat, Oct 18, 2025, 7:46 PM UTC

ahartmetz wrote: post #58

burntsushi wrote: post #37

Earlier quoted context omitted.

ripgrep is a lot faster (which you might only notice on larger haystacks), has many fewer bugs and is maintained.

ag is plenty fast (gigabytes in a fraction of a second) for me - I'd switch in a heartbeat if that wasn't so. Any bugs, hm, I guess I just haven't run into them. Thanks for the reply though! I realize who replied here ;)

    $ (time rg -wi '\w+(PM_RESUME|LINK_REQ)') | wc -l

    real    0.114
    user    0.547
    sys     0.543
    maxmem  29 MB
    faults  0
    444

    $ (time ag -wi '\w+(PM_RESUME|LINK_REQ)') | wc -l

    real    0.949
    user    6.618
    sys     0.805
    maxmem  65 MB
    faults  0
    444

    $ (time rg Openbox) | wc -l

    real    0.296
    user    1.349
    sys     1.950
    maxmem  71 MB
    faults  0
    11

    $ (time ag Openbox) | wc -l

    real    1.528
    user    1.849
    sys     8.285
    maxmem  29 MB
    faults  0
    11

    $ time ag '^\w{42}$' full.txt
    ERR: Skipping full.txt: pcre_exec() can't handle files larger than 2147483647 bytes.

Post by burntsushi » Sat, Oct 18, 2025, 7:58 PM UTC

kccqzy wrote: post #62

I discovered and started using the silver searcher (ag) before ripgrep existed. I don't feel a strong need to switch for marginally faster search but with different command-line switches. Am I missing some killer feature here?

    $ ag -c '\w{8,} Sherlock Holmes' sixteenth.txt
    9
    $ rg -c '\w{8,} Sherlock Holmes' sixteenth.txt
    9
    $ cat sixteenth.txt | rg -c '\w{8,} Sherlock Holmes'
    9
    $ cat sixteenth.txt | ag -c '\w{8,} Sherlock Holmes'
    1
    1
    1
    1
    1
    1
    1
    1
    1

    $ printf 'foo\nbar\n' | ag 'foo\s+bar'
    $ printf 'foo\nbar\n' | rg -U 'foo\s+bar'
    foo
    bar

    $ ag '\w+ Sherlock Holmes' full.txt
    ERR: Skipping full.txt: pcre_exec() can't handle files larger than 2147483647 bytes.

Post by winrid » Sat, Oct 18, 2025, 8:05 PM UTC

Post by burntsushi » Sat, Oct 18, 2025, 8:15 PM UTC

thdhhghgbhy wrote: post #66

burntsushi wrote: post #64

Earlier quoted context omitted.

What do you mean? You could pass an empty pattern. But that will match everything. Maybe talk about your use case at a higher level.

Thanks for the response. I would like to use fzf with rg to search file contents with a previewer open. However when I first open fzf I don't wish to pass any argument to rg, until I start typing. Something like Telescope live_grep.

Post by oever » Sat, Oct 18, 2025, 8:41 PM UTC

burntsushi wrote: post #53

oever wrote: post #49

Earlier quoted context omitted.

The point is to search hidden files that are tracked by git. An example is CI scripts which are stored in places like .woodpecker, .forgejo, .gitlab-ci-yml.

One thing you might consider to make this more streamlined for you is this: $ printf '!.woodpecker\n!.forgejo\n!.gitlab-ci-yml\n' > .rgignore Or whatever you need to whitelist specific hidden directories/files. For example, ripgrep has `!/.github/` in its `.ignore` file at the root of the repository[1]. By adding the `!`, these files get whitelisted even though they are hidden. Then `rg` with no extra arguments will…