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:
# Put this in your .bashrc file
.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: email@example.com/what-is-th...
I recommend revising the text accordingly.
here a gist alias
Nice post, btw there is no need to alias home. Just type 'cd' without parameters and it will bring you $HOME.
I didn't know this! Thank you for sharing!
## arrow up
## arrow down
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...
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.