🚀 go-pugleaf

On 06/07/2018 06:18 AM, Jorgen Grahn wrote:
> seems to me overriding a standard utility would almost always be the 
> wrong solution to a problem.

Maybe, maybe not.

Keep in mind, I'm only superseding / augmenting system commands that I 
want to run differently than they do by default.

I have ~/bin first in my path.  I have a number of utilities that 
require root permission (gained via sudo) that I run ALL THE TIME (as in 
daily, some many times a day).

So I have a wrapper [1] that I put in ~/bin for things like ip, netstat, 
ifconfig, route, etc so that I can type commands into my unprivileged 
user's shell exactly the same way that I would type them in root's shell.

I don't have to worry about needing to prefix commands with sudo (et al) 
or not.
I don't have to worry about using different formats of commands in 
different contexts.
I don't have to worry about escaping special characters to make it 
through sudo.
Etc.

I personally consider removing all the above mental load and making the 
computer do what I want to be a good thing.  Thus I consider it to be 
the proper solution.

There is also the fact that I have a LOT of commands in ~/bin that don't 
exist anywhere else that I use hourly (while at the computer).  So 
having them in a directory that is last in the PATH means that the shell 
has to traverse more directories to find them.

Aside:  I use a lot of extremely small shell scripts instead of aliases 
because I want to also be able to use the same shell scripts from within 
other locations where aliases don't apply, like non-interactive ssh 
remote command execution or other shell scripts.

What if I want a specific version of a command later in the PATH 
priority that gets superseded by a different version that is earlier in 
the PATH priority?  Having ~/bin first in the PATH allows me to make a 
sym-link to the version that I want.  Thus the version that I want is 
found and supersedes the version I want to avoid.

Finally, remember that we're talking about a user's PATH, not the system 
wide PATH.  Which means (to me) that it's up to the given user to 
configure things the way that they want.  Far be it for me to tell you 
what you should and should not do.

[1] Link - Sudify
      - https://dotfiles.tnetconsulting.net/tools/sudify/sudify.html



-- 
Grant. . . .
unix || die