I’ve done something similiar to this over the years for organization purposes and not having to change much between shells except add a path. You can also add cases that check your shell and do something slightly different if needed.
I’ve done something similiar to this over the years for organization purposes and not having to change much between shells except add a path. You can also add cases that check your shell and do something slightly different if needed.
I have never heard of anyone using aliases for anything but trivial one-liners. I don’t think people consider them as an alternative to scripts so I don’t really get the point of half of this post.
However, the part explaining the benefits of using scripts over aliases even for trivial one-liners is pretty neat.
I honestly thought he was kidding when I came across the g=git example.
I use aliases for renaming commands and making bash scripts look like real commands to the rest of my team.
Why not make them executable and stick them in bin
Mostly because there’s a profile everyone sources that’s relatively straightforward to that’s straightforward to get access to. Whereas I’d never get root level access.