True, 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?