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.
replyHow 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)
replyI wrote Ripgrep.
replyAnd they wrote "... you'd need to pick a side and lose the pun.."
replyAnd I am able to read four sentences.
replyIt’s only 2 characters - if you use it all the time it becomes muscle memory.
replyYou can simply add a shell alias with whatever name you like and move on.
replyTrue, but easier said than done, because one often need to work in more shells than their local machines..
replyThis is a nonstandard tool. If you can't customize your machine, you already don't have it.
replyBut it could be one day..
replyDo something like this to fall back to plain grep. You will somehow have to share these configurations across machines though.
reply alias g=grep
command -v rg 2>&1/dev/null && alias g=rgYou can't in most corporate env machines.
replyYou may be able to download ripgrep, and execute it (!), but god forbid you can create an alias in your shell in a persistant manner.
huh? If you can download and execute files, you can alias it. Either in your .bashrc file, or by making a symlink.
replyI daily drive linux, but I hop from clients to clients and I have probably served about 200 different structures so far.
replyMost 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.
How can you possibly get development work done in an environment where you can even make a Microsoft.PowerShell_profile.ps1?
reply`[citation needed]`
reply> You can't in most corporate env machines.
replyReally? "most" even? What CAN you do if you can't edit files in your own $HOME?
Don't get me started on `nvim` to run neovim...
replyThis 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.
reply