The terminal isnβt the most user friendly - sensitive to errors, challenging to read, and it requires a lot of typing! I frequently find myself ty...
For further actions, you may consider blocking this person and/or reporting abuse
Great post! Aliases really makes things easy and short. In addition, if you are using bash, you can put your aliases on
~/.bashrc
. That way, you won't have to execute~/.custom_bash_commands
for every session.I have my aliases in one dotfile, functions in another, then I source both in my .bashrc
I like keeping them separate for cleanliness and testing while also having them sourced in every session automatically.
That's awesome organization! I think as I gain experience and discover which functions I'll want as shortcuts I'll restructure how I've saved these functions.
Or better yet ask .bashrc to reference ~/.custom_bash_commands at login:
.bash_profile and .bashrc are two semantically different files. Both can be found on both linux and osx (which is also a linux os because it has linux kernel).
Difference between .bash_profile and .bashrc is explained here: medium.com/@kingnand.90/what-is-th...
I recommend revising the text accordingly.
My
.inputrc
here a gist alias
gist.github.com/hightemp/5071909
Thank you so much, this is awesome!
I had recently created a simple tool that allows me to simply add aliases without editing .bashrc files every time. github.com/pushkar-anand/bashAlias...
I didn't know this! Thank you for sharing!