Have had many hats on in my life: Developer, Team Lead, Scrum Master, Architect and Product Owner. Now back to developer \o/ Interested in product discovery, quality assurance and language design.
I'd recommend starting all alias names with a common prefix, so that you can list the available aliases with tab-completion. Something uncommon like dk or something. Then you can do dk<TAB> and see all your aliases.
Good to know I am not the only one with this idea. I prefix all my tool related alias like fld_prune = docker system prune and flk_delete = kubectl delete. fl is my handler, fld_ are my docker alias, flk_ are kube related aliases. fly_ are youtube-dl related alias. Only tools related aliases are prefixed, common aliases are not prefixed so cls=clear and md=mkdir -p are unprefixed.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice cheat-sheet, thanks!
I can add:
I'd recommend starting all alias names with a common prefix, so that you can list the available aliases with tab-completion. Something uncommon like
dkor something. Then you can dodk<TAB>and see all your aliases.Good to know I am not the only one with this idea. I prefix all my tool related alias like
fld_prune = docker system pruneandflk_delete = kubectl delete.flis my handler,fld_are my docker alias,flk_are kube related aliases.fly_are youtube-dl related alias. Only tools related aliases are prefixed, common aliases are not prefixed socls=clearandmd=mkdir -pare unprefixed.