Live data from Hacker News

“You meant to install ripgrep”

crates.io

91–100 of 165 posts

Re: “You meant to install ripgrep”

#91

Hah! TIL. I had no idea someone did this. But it's smart. I should have thought of it! (I'm the author of ripgrep.)

Unrelated, but thank you for your work!

You’ve saved me tens if not hundreds of hours with ripgrep, and I’ve become a huge evangelist of it at my workplace. When I’m helping someone understand how to debug customer issues, the first thing I tell them is to install ripgrep. Truly a fantastic piece of software.

Re: “You meant to install ripgrep”

#92
post #30
post #10

Earlier quoted context omitted.

You should not have done this unless you want to further normalize the practice of namespace squatting. This is the same type of behavior leads to domain squatting. While arguably being slightly more benign in the sense of hedging against typosquatting, if everyone started going things like that, we'd quickly begin to run into namespace exhaustion problems as people started ballooning their package namespace footprin…

I'd like to note there are three perverse incentives that lead to abuses of public namespaces (that I am aware of - please tell me if I've missed any): 1.) The use of names as a speculative financial instrument (in all shades of grey, up to and including extortion for lapsed or stolen names) 2.) The use of names as vectors of attack, such as by exploiting typos or homographs (such as malicious packages) 3.) The reser…

>#2 is endemic to all package managers.

It is endemic to package managers which don't do curation, which is why I'm a fan of package managers that do.

Re: “You meant to install ripgrep”

#93

Hah! TIL. I had no idea someone did this. But it's smart. I should have thought of it! (I'm the author of ripgrep.)

Just want to thank you for ripgrep and your other rust contributions. Ripgrep is insanely powerful and is absolutely indispensable for me.

Re: “You meant to install ripgrep”

#94
post #44

Earlier quoted context omitted.

I use ripgrep on git bash for Windows, and my team members act like I’ve got searching superpowers. Searching on windows is such a pain and this makes it easy. Thanks so much for making this fantastic tool!

doesn't vscode use ripgrep under the hood when you search your open files/repos?

Yes. But you might not be using VS Code. :-)

Re: “You meant to install ripgrep”

#95
post #91

Hah! TIL. I had no idea someone did this. But it's smart. I should have thought of it! (I'm the author of ripgrep.)

Unrelated, but thank you for your work! You’ve saved me tens if not hundreds of hours with ripgrep, and I’ve become a huge evangelist of it at my workplace. When I’m helping someone understand how to debug customer issues, the first thing I tell them is to install ripgrep. Truly a fantastic piece of software.

w00t! Thanks for the kind words. :-)

Re: “You meant to install ripgrep”

#96
post #30

Earlier quoted context omitted.

I'd like to note there are three perverse incentives that lead to abuses of public namespaces (that I am aware of - please tell me if I've missed any): 1.) The use of names as a speculative financial instrument (in all shades of grey, up to and including extortion for lapsed or stolen names) 2.) The use of names as vectors of attack, such as by exploiting typos or homographs (such as malicious packages) 3.) The reser…

>#2 is endemic to all package managers. It is endemic to package managers which don't do curation, which is why I'm a fan of package managers that do.

Sure. Really I meant "language community package registries," which are necessarily open bazaars from which more selective repositories can be drawn.

Re: “You meant to install ripgrep”

#97
post #73

Earlier quoted context omitted.

I love that ripgrep honors .gitignore, but the fact that it skips hidden files is annoying because of questionable decisions from tool makers who insist their configuration files should be hidden files. It is especially infuriating when working with GitHub and GitLab configuration directories. On the other hand I never want ripgrep to enter the .git directory. I recently came up with this alias to make ripgrep do wha…

Yeah that alias is a good one, here are some other avenues: * The repo can add a `.ignore` or a `.rgignore` whitelisting things like `.github`. ripgrep will pick up that whitelist automatically and search `.github` even though it's hidden. But this relies on the repo adding ripgrep-specific config files, which is maybe not so realistic. (Or not universal enough to rely upon.) But it could work fine for repos under yo…

I use ripgrep everywhere, not only in my own repositories, so the first approach won't work for me. The second one, on the other hand, sounds like a really good idea, going to look into it, thanks.

And of course, thanks for this wonderful tool!

Re: “You meant to install ripgrep”

#99
post #55
post #53

What is ripgrep? Edit: Because I'm on a Zoom call that will never end. "ripgrep is a line-oriented search tool that recursively searches the current directory for a regex pattern. By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files." https://github.com/BurntSushi/ripgrep

A file searcher akin to grep, ack, or ag (aka the silver searcher) it's programmed in Rust so it is decently fast with good support for UTF-8. Unfortunately it defaults to parsing a git tree's gitignore file and skipping over files listed in it.

"decently fast" is a significant understatement. It is likely the fastest similar tool. (`git grep` may win due to not listing the directory tree and packed files and GNU grep is very fast if you don't use Unicode, but other than that ripgrep wins).
Post reply on HN