| ▲ | keybored 12 hours ago |
| > The binary name for `ripgrep` is `rg`. I don’t understand when people typeset some name in verbatim, lowercase, but then have another name for the actual command. That’s confusing to me. Programmers are too enarmored with lower-case names. Why not Ripgrep? Then I can surmise that there might not be some program ripgrep(1) (there might be a shorter version), since using capital letters is not traditional for CLI programs. Look at Stacked Git: https://stacked-git.github.io/ > Stacked Git, StGit for short, is an application for managing Git commits as a stack of patches. > ... The `stg` command line tool ... Now, I’ve been puzzled in the past when inputing `stgit` doesn’t work. But here they call it StGit for short and the actual command is typeset in verbatim (stg(1) would have also worked). |
|
| ▲ | qudat 10 hours ago | parent | next [-] |
| Because we are constantly writing variables that are lowercase. Coming up with a name that is both short but immediately understandable is what we live for. Variables are our shrine, we stare at them everyday and are used to their beauty and simplicity. |
|
| ▲ | Macha 10 hours ago | parent | prev | next [-] |
| How would you capitalise it? RipGrep? RIPGrep? You’d need to pick a side and lose the pun. (And of course grep itself would need to be GReP if we took it all the way) |
| |
|
| ▲ | orf 12 hours ago | parent | prev | next [-] |
| It’s only 2 characters - if you use it all the time it becomes muscle memory. |
|
| ▲ | lpapez 12 hours ago | parent | prev | next [-] |
| You can simply add a shell alias with whatever name you like and move on. |
| |
| ▲ | qsera 12 hours ago | parent | next [-] | | True, but easier said than done, because one often need to work in more shells than their local machines.. | | |
| ▲ | pie_flavor 11 hours ago | parent | next [-] | | This is a nonstandard tool. If you can't customize your machine, you already don't have it. | | | |
| ▲ | worksonmine 10 hours ago | parent | prev [-] | | Do something like this to fall back to plain grep. You will somehow have to share these configurations across machines though. alias g=grep
command -v rg 2>&1/dev/null && alias g=rg
|
| |
| ▲ | BiteCode_dev 11 hours ago | parent | prev [-] | | You can't in most corporate env machines. You may be able to download ripgrep, and execute it (!), but god forbid you can create an alias in your shell in a persistant manner. | | |
| ▲ | OkayPhysicist 3 hours ago | parent | next [-] | | huh? If you can download and execute files, you can alias it. Either in your .bashrc file, or by making a symlink. | | |
| ▲ | BiteCode_dev 2 hours ago | parent [-] | | I daily drive linux, but I hop from clients to clients and I have probably served about 200 different structures so far. Most corporate machines are Windows boxes with ps and cmd.exe heavily restricted, no admin, and anti malware software surveilling I/O like a hawk. You might get a git bash if you are lucky, but it's usually so slow it's completely unusable. In one client I once tried to sneak in Clink. Flagged instantly by security and reported to HR. It's easy to forget that life outside the HN bubble is still stuck there. |
| |
| ▲ | pentaphobe 9 hours ago | parent | prev | next [-] | | `[citation needed]` | |
| ▲ | worksonmine 10 hours ago | parent | prev [-] | | > You can't in most corporate env machines. Really? "most" even? What CAN you do if you can't edit files in your own $HOME? |
|
|
|
| ▲ | vortegne 10 hours ago | parent | prev [-] |
| Don't get me started on `nvim` to run neovim... |
| |
| ▲ | opan 6 hours ago | parent [-] | | This was my first thought as well. I think I end up just calling it nvim sometimes even conversationally, the binary name is the most "real" thing to me. |
|
