Aliases and bash customization

Objectives:

Create aliases. >

Add customizations to the .bashrc and .bash_profile files. >

Change the prompt in a bash environment.

TL;DR

Aliases are used to create shortcuts or abbreviations >

The .bashrc and .bash_profile files allow us to customize our bash environment. >

The PS1 system variable can be changed to customize your bash prompt.

Bash allows us to customize our environments to fill our own particular needs.

Aliases

Sometimes we need to use long commands that have to be typed over and over again. Fortunately, the alias command allows us to create shortcuts for these long commands.

As an example, let's create aliases for going up one, two, or three directories.

alias up='cd ..'
alias upup='cd ../..'
alias upupup='cd ../../..'

Let's try these commands out.

cd /usr/local/bin
upup
pwd

Output:.

/usr

We can also remove a shortcut with unalias.

unalias upupup

If we create one of these aliases in a bash session, they will only last until the end of that session. Fortunately, bash allows us to specify customizations that will work whenever we begin a new bash session.

Bash customization files

Bash environments can be customized by adding commands to the .bashrc, .bash_profile, and .bash_logout files in our home directory. The .bashrc file is executed whenever entering interactive non-login shells whereas .bash_profile is executed for login shells. If the .bash_logout file exists, then it will be run after exiting a shell session.

Let's add the above commands to our .bashrc file.

Be careful to append to .bashrc, with >>. for concatenate, rather than one > which would overwrite.

echo "alias up='cd ..'" >> ~/.bashrc
tail -n 1 ~/.bashrc

Output:

alias up='cd ..'

We can execute the commands in .bashrc using source, so this creates the alias up which we can then use in directory /usr/local/bin:

source ~/.bashrc
cd /usr/local/bin
up
pwd

Output:

/usr/local

Having to add customizations to two files can be cumbersome. It we would like to always use the customizations in our .bashrc file, then we can add the following lines to our .bash_profile file.

if [ -f $HOME/.bashrc ]; then
        source $HOME/.bashrc
fi

Furthermore, and what is seen as good practice it to have a seperate alias file which is sourced in a similar way.

if [ -f $HOME/.bash_aliases ]; then
        source $HOME/.bash_aliases
fi

Within this file you could place

#GIT
alias gst="git status"
alias ga="git add"
alias gaa="git add ."
alias gcm="git commit -m"
alias gpl="git pull"
alias gps="git push"
gc ()
{
  git clone git@github.com:"$1""/""$2"
}

alias ls="lsd"
alias layout="~/.config/i3/layouts/layout.sh"
alias off="sudo shutdown -h now"
alias cat="bat -p"
alias cccu="cd ~/Universities/CCCU/"

Of course, alias cat="bat -p", "alias cccu="cd ~/Universities/CCCU/"",alias layout="~/.config/i3/layouts/layout.sh",alias ls="lsd"... will not work on your system unless you have the same packaged, file structure etc.