HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
BurntSushi
ripgrep
Rust2016–2026
BurntSushi / ripgrep

ripgrep

ripgrep recursively searches directories for a regex pattern while respecting your gitignore

196Distinct people
333Mentions
9Explicit recommenders
69.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

ripgrep recursively searches directories for a regex pattern while respecting your gitignore

GitHub

Where it is used

  • Visual Studio Code — Visual Studio Code uses ripgrep to power its text search feature, making searches faster. This integrates ripgrep as the engine behind VS Code’s search. Source
  • Eclipse Theia — Eclipse Theia installs and uses ripgrep under its install directory (resources/app/lib/backend/native/ripgrep), requiring extensions to point to that location because Theia places ripgrep in a different directory than VSCode. Source

What people are saying

> I wrote about how to do error handling without libraries literally the day Rust 1.0 was published: https://burntsushi.net/rust-error-handling/ > > That blog did include a…

osiris88 used a recommendation phrase. 9 indexed comments match. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year333 dated mentions

Observed mentions: 2016-09-23 15:29:58 UTC to 2026-10-05 14:38:02 UTC.

010203040502016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 25 mentions; 1 submissions, 24 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 34 mentions; 3 submissions, 31 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 41 mentions; 5 submissions, 36 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 41 mentions; 1 submissions, 40 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 45 mentions; 3 submissions, 42 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 37 mentions; 2 submissions, 35 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 29 mentions; 1 submissions, 28 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 32 mentions; 3 submissions, 29 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 14 mentions; 2 submissions, 12 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 21 mentions; 3 submissions, 18 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 14 mentions; 4 submissions, 10 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC25124
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC34331
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC41536
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC41140
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC45342
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC37235
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC29128
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC32329
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC14212
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC21318
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC14410

What Hacker News says

29 sources
Powershell actually ships one! I think you have a good point. I was going to build my own as C# ships alot of configuration options that can DRASTICALLY improve speed, which arn't on by default. But, we can test Redmonds version and get at least a decent idea of if it's suitable. I'll run some tests on that and get back to you in an hour or so. I'll use the same tests you have on https://github.com/BurntSushi/ripgrep/blob/master/benchsuite... My testing will be on my Dev VM, in a WSL container on ubuntu 22.04, targeting a built linux kernel. With powershell from the Microsoft blobs they ship for linux. And Ripgrep from just Apt Install Ripgrep. With 5 warmup cycles for each.
In How I got involved in the Rust community
I see no benefits in using Warp over a regular (and more supported) GPU-accelerated terminal emulator. It's just "prettier" out of the box, and it seems to market quite a bit to people that either don't know how to configure their shells, or don't know what they're doing. - If you want fuzzy command, history, file / contents search, use fzf [0] (you should probably be using fzf and ripgrep [1] anyway if you work daily in your terminal). - If you want sessions, use a multiplexer like tmux [2] or zellij [3]. - If you need to have your own "cheatsheets" use navi [4]. If you want to sync them with your team, use whatever sync solution you like. - If you think you need a text editor in your shell's command line, reconsider. If you *really* want to edit and re-execute the last command in your editor of choice, use something like "fc $!
Read the rest
" [5] or create your own shell solution for it. - If you want a sexy prompt use starship [6]. - If you want terminal sharing use tty-share [7]. - If you want to ask GPT for help, don't do it in your terminal. Open up ChatGPT (or whatever future UI will exist), ask your question, and check that there's nothing harmful in what your about to execute. Sometimes friction is good. For each of these ^ pieces of software there are tens and hundreds of alternatives. If you want a terminal that's pretty out-of-the-box, where things are "clickable", you don't have the time or interest to invest your energy in learning tools that could massively boost your productivity for years to come, and you don't care about designing your own workflow and being able swap parts of it at any point, without depending on any single "app", and if you don't mind "logging into your terminal" (what the actual fuck, excuse the language) or the terminal adding its own SSH wrapper and doing things you don't know to the hosts you connect, then maybe Warp is OK for you. But then again, maybe you're not going in the right direction. There are so many more awesome ways you could improve your shell experience than making things clicky. I don't understand what the market is for Warp, is it for wanna-be professionals that can't be bothered to become professionals? I completely fail to see how this could succeed as a paid product, especially with a subscription model. [0] https://github.com/junegunn/fzf [1] https://github.com/BurntSushi/ripgrep [2] https://github.com/tmux/tmux [3] https://github.com/zellij-org/zellij [4] https://github.com/denisidoro/navi [5] https://shapeshed.com/unix-fc [6] https://starship.rs/ [7] https://github.com/elisescu/tty-share
In Telemetry is now optional in Warp
The same thing happens to me and IMO almost always these are enough: - HN Search website [0] (with the use of search operators), almost always I remember a keyword from the title and restrict the search between dates (or sort by date if is something recent). - History Trends Unlimited chrome extension [1], in case I remember the domain. - A local "personal knowledge base" / "digital garden" / "second brain" [2], in case I want to remember, review, and/or update my notes. "Local" to speed up search (with `ripgrep`[3]) [0] https://hn.algolia.com/ [1] https://chrome.google.com/webstore/detail/history-trends-unl... [2] https://en.wikipedia.org/wiki/Personal_knowledge_base [3] https://github.com/BurntSushi/ripgrep
In Ask HN: Bookmarks for Hacker News?
Even if sed and grep are available their weird syntax is enough to make people write modern replacements. I don't care if they're not 100% feature complete, the fact I can remember how to use them for my simple everday tasks (searching, finding/replacing across many files) without needing to consult a manpage or search online for answers is enough. I used grep daily for years and _still_ it didn't feel like it made sense. I remember reading about Ack (https://beyondgrep.com/) some time in 2009-2010 , installing it and switching over entirely within about five minutes. Modern sed: https://github.com/chmln/sd Modern grep: https://github.com/ggreer/the_silver_searcher https://github.com/BurntSushi/ripgrep
In Being Ridiculed for My Open Source Project (2013)
The extra discipline I'm talking about has to do with curating the commits in order to make them meaningful. Here's an example of this from the wild: https://github.com/BurntSushi/ripgrep/pull/350#issuecomment-... BurntSushi (the project maintainer) didn't care about the story the commits told, he cared about the entirety of the changes being made to the repo (at the PR level). > What's lost is the ability to make code contributions of related changes together in a PR You're considering each minor commit to be an independent code contribution. BurntSushi instead considered the PR to be the code contribution. The code changes are the same either way you look at it, and there is a single PR in both cases, so it's a matter of choosing your perspective.
In Git commit messages are useless
Bud, this was the extent of your exchange that was apparently "too subtle" for all us dumbfucks to understand: >>> So it's grep like i already have installed and know its quirks? >> yeah but with less quirks and runs much faster. worth trying out > Uses regexes = has quirks. So you start off with a passive aggressive nose snubbing. Someone comes in and spends exactly as much time on you as you deserve, and describes ripgrep in their own words by saying it has "less quirks." And indeed, a lot of people experience that precisely because ripgrep uses heuristics to reduce false positives in search results. Many folks experience that as "less quirks." You might not and many others might not, but that ain't their problem. Then you respond with "uses regex = has quirks," as if the parent said "ripgrep has no quirks." Well, no shit s
Read the rest
herlock, any grep is going to have regex support and any grep is going to have the quirks that come with regexes. That doesn't mean what the parent poster said was incorrect and it certainly doesn't mean the parent poster implied ripgrep had zero quirks. Your comment was a refutation of a silly straw man. Real subtle, I know. > Readme was not linked here. I looked and didn't find it in the parent link. Feel free to abuse my competence or, you know, link it in the discussion? Actually I'll do it. If this was a link to a blog post about ripgrep or a release announcement or something of that sort, yeah, absolutely, the author should have given ripgrep at least a short introduction and a link to the README. But this is just a link pointing out a typo-squatted crate meant to improve failure modes. It's a "hey here's something interesting." It isn't even interesting just because of ripgrep, it's interesting because some person cared enough to try and improve failure modes and prevent someone from installing the wrong thing. If you want to know what ripgrep is from there, it's on you to go figure it out. It isn't on your fellow HN commenters. They explained what it was in their own words and you didn't like it. And now you've spent who knows how much time here whinging about "herp derp hype and but but but signal-to-noise" when it would have taken you less than 5 seconds to Google the damn word and click on the first result. > A faster grep where some people find the defaults in the interface more usable, with some potentially interesting additional features. LOL. This is a terrible description. ripgrep's official description is shorter and far more useful, because it gives you an idea of what it's actually doing, instead of just vaguely talking about it: > ripgrep recursively searches directories for a regex pattern while respecting your gitignore Bottom line is: * You made silly snobbish comments. * The rest of your whinging could have been mitigated by a 5 second Google search. Yes, normally, for things like release announcements[1], I include a short blurb about what ripgrep is. But this wasn't a release announcement. You want the official answer? Then go look for it. You want the (possibly described in terms of their own experience) opinion of your HN peers? Well, that's what you got. Live with it. [1]: https://github.com/BurntSushi/ripgrep/releases/tag/13.0.0
In “You meant to install ripgrep”
Thanks for your response. Readme was not linked here. I looked and didn't find it in the parent link. Feel free to abuse my competence or, you know, link it in the discussion? Actually I'll do it. https://github.com/BurntSushi/ripgrep/blob/master/README.md There. That feels better doesn't it? More quirks you have to learn is not less. You know 5 quirks. This new thing has 3 /different/ quirks to perform the same task you already know. To use the thing with "less" quirks you need to know _more_ quirks. And that can be fine! Or you might decide it as not worthwhile. But it is more quirks you gotta learn. Pointing that out is not a non-sequitur to a discussion that starts with: >So it's grep like i already have installed and know its quirks? "Yes, and it's faster if you need that and its ui makes more sense to me." Is an appropriate addendum
Read the rest
. Less quirks means you gotta learn more. And that is just life for all of us and one of the barriers that protects incumbents that are in some sense not as good. Note my selfish comment was taking my perspective that I already have grep and I already use it and know its quirks. From your readme: >You need a portable and ubiquitous tool. While ripgrep works on Windows, macOS and Linux, it is not ubiquitous and it does not conform to any standard such as POSIX. The best tool for this job is good old grep. So you see how if you have to know grep anyway, less quirks isn't a great thing in and of itself to the user. Simpler to use interface, yeah that could be compelling. Or not. Faster could be compelling. Or not. Some additional feature could be compelling. Maybe ripgrep is amazing and the future and just dandy and I wish you the best of luck with everything you want to achieve with your version of grep. -------- >Your follow-up comment looks ever worse to be honest, and sounds like an argument for never building anything different at all That's basically pretty rude and difficult to reconcile with what I actually said. >ripgrep may well be a better grep for some users. And that is Great, really! We should all try and make things better! Hurrah! Q. What is ripgrep? A. A faster grep where some people find the defaults in the interface more usable, with some potentially interesting additional features. What a lot of words wasted to get to that Q & A. Please feel free to improve it while maintaining that length. Signal to noise.
In “You meant to install ripgrep”
100%. That the author think it's "backwards" that they can't run a sustainable business by copying what's already been made but need to put in some actual work (and that building profitable software inherently must involves AI/ML experts and cloud specialist) speaks more about OPs bias than about actual requirements. Not meaning to point fingers at them specifically too much; they're most likely in a bubble where these views are implicitly assumed. As for the specific example of Photoshop, well, yeah.. Adobe has put in at least that much work and resources behind it, so what do you expect is required to get a fair fight? Photoshop was an incredibly complex and refined piece of software with immense work behind it before they moved to the cloud. 99% you wouldn't pull that off in 2008 either. That GIMP is still mostly unheard of outside of
Read the rest
enthusiast circles and never posed any threat to Adobe shows that it takes way more than a handful of skilled devs. > Copies of grep https://github.com/BurntSushi/ripgrep started in 2016 and went stable in 2019. It's not being sold as a SaaS subscription because why would it? I often hear complaints about entitled users but I get some "entitled tech founder" vibes here, as if not being able to sustain on rent-seeking behavior is a defect.
In Time Till Open Source Alternative

Showing the 15 most recent of 29 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.