4 ms·
I tend to give programs longer, more descriptive names and then do the short names as shell aliases. That way there’s little risk of name collision for the orig
by aendruk 4y ago
I tend to give programs longer, more descriptive names and then do the short names as shell aliases. That way there’s little risk of name collision for the original program, scripts using the canonical name remain readable, and the shorthand is free to evolve to fit varying work habits.
- quasarj 4y agoMy keyboard came with a tab key, so I don't worry about my commands having short names.
- keybored 4y agoUntil you have five commands which all use the prefix `sort-incoming-` and then three commands named `sort-incoming-hourly` and `sort-incoming-monthly` etc.
- layer8 4y agoIt would be nice to have camel-case completion in the shell, i.e. have “SIH” be completed to “SortIncomingHourly” and “SIM” to “SortIncomingMonthly”, etc. (only for upper-case characters). That way one could get more mileage out of the possible character combinations.
- andra_nl 4y agoWell, not exactly tab completion, but I have `fzf`[0] tied to my history search. That allows me to type `soriloco`, punch ctrl+r and be prompted with `some ridiculously long command` (if, of course, I've run it before). Combined with infinite history this trick has saved me a bunch of typing and even proper remembering. :P [0]: https://github.com/junegunn/fzf https://github.com/junegunn/fzf
- keybored 4y agoYes, fuzzy matching is the way to go. Tab completion isn’t good enough any more.
- bergenty 4y agoWhy do the names have to be shorter, I never have to type it all out just the first couple of letters and then autocomplete. Dealing with aliases/“shortcuts” is such a pain plus I hate that pattern anyways.