re: 4 Simple Steps For Custom Bash Commands VIEW POST

FULL DISCUSSION
 

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
source ~/.custom_bash_commands
code of conduct - report abuse