Comment by Seirdy
6 years ago
Although this seems like a good idea, I wouldn't like typing an extra symbol. Maybe I'm just irrational.
Instead of prefixing my commands, I just search for a command in a manpage repo, cht.sh [0], and with my package manager (`dnf provides` for the DNF package manager). If nothing shows up, I'm probably safe. The process is easy to automate.
The problem is meant to deal with future conflicts as well as present ones, and re-checking on every update would be a pain. The more memorable and natural your aliases, the more likely they are to get clobbered later ….
Typing a comma is too hard, but that 4-step jerry-rig isn't?
It isn't "too hard" for me; it's just one of my irrational personal preferences. I don't claim that my solution is more efficient; I just don't like typing a leading comma and I think this "feels" more pleasant for me, and perhaps a few others.
He does that check once, when he's deciding on what to name it, not every time he runs the command.
This, plus I also said "Maybe I'm just irrational".
There is also the other advantage pointed out in the article, in that typing a comma and hitting tab lists all his custom commands.
All my scripts are in one directory [0] that's added to the front of my $PATH [1]; listing files in it would be trivial.
The author's solution does seem much better; I just use my approach instead because I don't like the feeling of typing a leading comma :). I might switch to using a leading char sometime.
[0]: https://git.sr.ht/~seirdy/dotfiles/tree/master/Executables/s...
[1]: https://git.sr.ht/~seirdy/dotfiles/tree/master/startup.sh#L1...