Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I would like to create an alias to rm command in order to have a confirmation message after executing this command. So I am creating an alias like this alias rm='rm -i'. But as far as I know this is a temporary alias and it lives until you close the terminal.

As it is explained here to save alias permanently I need to execute ~/.bash_aliases or ~/.bashrc commands in terminal and add my alias there. But when I execute ~/.bashrc I get following error message :

bash: /home/bakhtiyor/.bashrc: Permission denied

When I run ~/.bash_aliases I get another error message like this:

bash: /home/bakhtiyor/.bash_aliases: File or directory doesn't exist.

What is the actual problem and how can I solve it?

share|improve this question
    
How did you create an alias?? –  karthick87 Dec 15 '10 at 8:05
    
@karthick87. I have updated my question. –  Bakhtiyor Dec 15 '10 at 8:17
add comment

6 Answers

up vote 36 down vote accepted

To create an alias permanently add the alias to your .bashrc file

gedit ~/.bashrc

And then add your alias at the bottom.

alt text

Now execute . ~/.bashrc in your terminal (there should be a gap between the . and ~/.bashrc.

Now you can check your alias.

alt text

share|improve this answer
5  
He shouldn't need sudo to edit his own .bashrc file. Using ~ ensures he's editing the right one so it's harmless, but not required. –  Nerdfest Dec 15 '10 at 10:48
    
Thank you very much. –  Bakhtiyor Dec 15 '10 at 11:05
    
What about the system-wide bashrc file. It's in /etc/bashrc on CentOS. –  Buttle Butkus Nov 29 '12 at 9:22
1  
@ButtleButkus - sadly, some here don't have any concept of other operating systems... –  Wilf Jan 14 at 17:40
    
@karthick87 you wrote "Now execute . ~/.bashrc in your terminal (there should be a gap between the . and ~/.bashrc.". Why is this step needed? –  Geek Feb 11 at 15:21
add comment

There are lot of ways to create alias . The most used ways are :

1) . Add aliases directly in your ~/.bashrc file

For example. append these line to ~/.bashrc file

alias ll='ls -l'
alias rm='rm -i'

Next time when you type rm the rm -i command will be executed.

2). The second method lets you make a separate aliases file, so you won't have to put them in .bashrc, but to a file of your choice. First, edit your ~/.bashrc file and add or uncomment the following lines, if it is not already

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

Save it and close the file. After that, all you have to do is create a ~/.bash_aliases file and add your aliases there, with the same format specified in the first method.

Contents of my ~/.bash_aliases file:

aneesh@aneesh-VirtualBox:~$ cat .bash_aliases 
alias cs='cd;ls'
share|improve this answer
12  
+1 for using ~/.bash_aliases. –  ændrük Jun 10 '11 at 5:48
add comment

The problem is that you are trying to execute a non executable file: You can check this with:

ls -la ~/.bashrc
-rw-r--r-- 1 username username 3596 2010-08-05 17:17 /home/pt001424/.bashrc

Note there is no "x - executable" letter on the first column (file permissions).

Profile files are not executable files, instead of executing them you load them with:

source /home/bakhtiyor/.bashrc

or

. /home/bakhtiyor/.bashrc
share|improve this answer
add comment

It sounds to me like your only problem is simply trying to execute .bashrc when it is not executable. But this isn't the correct way to do it; whenever you make a change to this file, you should "execute" it by the command:

source ~/.bashrc

Otherwise, it will simply create a new shell, execute the file in the new shell's environment, then discard that environment when it exits, thereby losing your change. By sourcing the script, it executes within the current shell, so it will remain in effect.

I'm assuming the second error was because bash_aliases does not exist. It is not required, just recommended to keep your changes separate and organized. It is only used if it exists, and you can see the test for it in .bashrc:

if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi

This says that if the file ~/.bash_aliases exists, then run it.

share|improve this answer
add comment
echo "alias vps='ssh -X user@example.com'" >> ~/.bashrc

This is an example I was looking for, a way to type a few letters at the terminal ("vps") to remotely log in to a server and enable X11 forwarding so I can run gui apps like "gedit" over the network.

Whatever the command / aliased command, this way with the echo statement, quotation marks, and the symbol for appending the output of a command to a file (>>) works for me. Just replace my command for the alias command you need and enter it into your terminal.

share|improve this answer
add comment

I've made this little function for quickly writing a new-alias to .bashrc

##------------------------------------ ##
 #           -- new-alias --           #
 # creates new alias & writes to file  #
 #          $1 = alias new             #
 #          $2 = alias definition      #
##------------------------------------ ##
new-alias () { 
  if [ -z "$1" ]; then
    echo "alias name:"
    read NAME
  else
    NAME=$1
  fi

  if [ -z "$2" ]; then
    echo "alias definition:"
    read DEFINTION
  else
    if [ "$2" = "-cd" ]; then
      DEFINTION='cd '
    else
      DEFINTION=$2
    fi
  fi

  echo "alias $NAME='$DEFINTION'" >> ~/.bashrc
  . ~/.bashrc
}
share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.