Live data from Hacker News

“You meant to install ripgrep”

crates.io

51–60 of 165 posts

Re: “You meant to install ripgrep”

#52
post #32

Earlier quoted context omitted.

I guess "owner/packagename" convention could solve such issues as it's common with other package ecosystems.

Right. So then you add burnsushi/ripgrep instead. See the problem? Namespaces are a solution or mitigation to some problem, but that problem is not malicious typo-squatting.

>See the problem?

The only problem I see is that I don't know who owns ripgrep, so sticking some random name in front of it only adds to my confusion.

Re: “You meant to install ripgrep”

#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

Re: “You meant to install ripgrep”

#54
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 grep alternative that optimizes for performance: https://github.com/BurntSushi/ripgrep . There are detailed performance comparisons and discussions in the readme there.

Re: “You meant to install ripgrep”

#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.

Re: “You meant to install ripgrep”

#56
post #43

Earlier quoted context omitted.

To me the problem solved by namespaces is making it clear what's an official package of a project and what's a non-malicious third party package intended to work with that project. e.g. bevy and amethyst have claimed a load of crate names like bevy-x or amethyst_y because they thought they might release an official addon to their framework to handle those areas. e.g. bevy did it with this https://github.com/bevyengin…

I'm not sure I necessarily agree with that... But yeah I specifically did not want to get into what namespaces do solve, and so was instead vague and just acknowledged that they're good for something . :-) I will also say this: at the level of personal preference, and given my understanding of many other package ecosystems, I would have preferred namespaces from the start. But I don't feel very strongly one way or th…

I edited to clarify.

Re: “You meant to install ripgrep”

#59
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.

> it defaults to parsing a git tree's gitignore file and skipping over files listed in it

Is that true? How could anybody think that this non-orthogonal monstrosity would make any sense?

Re: “You meant to install ripgrep”

#60
post #55

Earlier quoted context omitted.

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.

> it defaults to parsing a git tree's gitignore file and skipping over files listed in it Is that true? How could anybody think that this non-orthogonal monstrosity would make any sense?

It’s what you usually want when searching code bases. It includes all your source code but excludes generated code and build artefacts.
Post reply on HN