Why not just add ripgrep as a dependency, effectively making it an alias of the original package?
“You meant to install ripgrep”
71–80 of 165 posts
Re: “You meant to install ripgrep”
#72Why not just add ripgrep as a dependency, effectively making it an alias of the original package?
Maybe it's only for me, but I've never liked this of too-smart solutions. Let people do the mistakes once and learn the correct package name, instead of relying on a hack and potentially introduce confusion later.
Re: “You meant to install ripgrep”
#73Earlier 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 also defaults to ignoring hidden and binary files. It's also simultaneously the thing folks cite as their favorite part about ripgrep. The idea behind it is that it acts a heuristic for reducing false positives from your search results. For example, ripgrep replaced several little grep wrapper scripts I had in ~/bin. And fortunately the default behavior is easy to disable. `rg -uuu foo` will search the same stuff…
I recently came up with this alias to make ripgrep do what I want: do not skip hidden files, except for the .git directory:
alias rg="rg --hidden --glob '!.git/'"
(Note: if you try entering this alias interactively, you may have to escape the '!'...)
Re: “You meant to install ripgrep”
#74Earlier quoted context omitted.
Also bs4 / beautifulsoup4
These are both like numpy & pandas in always documenting with `import longname as ln` right? I think they bring it on themselves.
(and `pip install beautifulsoup4` lets you `import bs4`)
Re: “You meant to install ripgrep”
#75Crates should be namespaced by user. This is a disaster waiting to happen.
If you have `ripgrep-team/ripgrep` rather than `ripgrep`, it doesn't help at all with people typing the wrong thing, like `rg-team/rg`. I fail to see how it helps.
It's even worse with packages that are (currently) authored by a single person, how many people know the name of ripgrep's author? Or rand? Or bevy?
Re: “You meant to install ripgrep”
#76Hah! TIL. I had no idea someone did this. But it's smart. I should have thought of it! (I'm the author of ripgrep.)
Re: “You meant to install ripgrep”
#77Hah! TIL. I had no idea someone did this. But it's smart. I should have thought of it! (I'm the author of ripgrep.)
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!
Re: “You meant to install ripgrep”
#78Why not just add ripgrep as a dependency, effectively making it an alias of the original package?
Re: “You meant to install ripgrep”
#79This classic version of this in the Ruby ecosystem is "bundle"[1], which helpfully installs `bundler` for you. Of the 6.7 million downloads it has, I'm probably in there a dozen or so times. [1]: https://rubygems.org/gems/bundle
Re: “You meant to install ripgrep”
#80What 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.