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.

	▲	qsera 10 hours ago \| parent [-]
		But it could be one day..

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

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]`

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