4 ms·
Have you worked in a monorepo? There can be 100kloc or more, easily, as well as tens or hundreds of gigabytes for build artifacts/ compilation artifacts, etc th
by staticassertion 4y ago
Have you worked in a monorepo? There can be 100kloc or more, easily, as well as tens or hundreds of gigabytes for build artifacts/ compilation artifacts, etc that you'll want to skip over.
For scripts I'll still use grep sometimes for the portability reason, naturally.
- heywoodlh 4y agoI have not worked in a monorepo. But that seems to be a great place to use `ripgrep`.
- staticassertion 4y agoThat's probably the #2 thing for me. The other is that I have a `~/workspace` where I put all of my projects and sometimes I ripgrep through there.
- marcinreal 4y agoIt doesn't even have to be a monorepo to see the speed difference. In Emacs I frequently invoke a thing where it searches my codebase as I type. With ripgrep, the results update almost instantaneously. ag, the silver searcher, is the second fastest thing I've used, but there would be a noticeable lag in updating the results as I typed, even for smaller repos.
- jrockway 4y agoWhat's the emacs thing? I use deadgrep but your thing sounds better.
- deleted 4y ago[deleted]
- abzug 4y agoMy hunch is consult-ripgrep or counsel-rg.
- marcinreal 4y agoconsult-ripgrep as the other commenter said. Before that it was helm-rg.