3 ms·
For such folks, telling them that invoking the full path of the executable will bypass the alias, e.g. “/bin/rm -f” will do the right thing. Discoverable? Nah.
by kickingvegas 4y ago
For such folks, telling them that invoking the full path of the executable will bypass the alias, e.g. “/bin/rm -f” will do the right thing. Discoverable? Nah. But we are talking about shell command behavior which is pretty arcane anyways.
- bravetraveler 4y agoNot really something I'd suggest with rigor, but prefacing an aliased command with a backslash will also defeat it
- dylan604 4y agoTIL. I was unaware of that. so if rm is aliased to "rm -i", then \rm will do the normal thing?
- avnigo 4y agoYou can also do that by prefacing an aliased command with "command".
- dylan604 4y agoi like the \ vs 7+space additional key presses. that's like typing the full path without utilizing tab expansion. only noobs do that /s
- bravetraveler 4y agoIndeed! I had to use this pretty routinely supporting a particular customer at a previous employer. Their shell profiles were littered with two-letter aliases, replacing quite a few common things with their proprietary [often unrelated] versions For example, mv for moving files became mv for Mail Volume, or something
- dylan604 4y agodearlordy, that's even worse. aliasing an existing cmd with options preset is one thing. aliasing a well known cmd to some esoteric cmd is mindboggling