Terminal shows this
bash: /home/atlas/.bashrc: line 73: syntax error near unexpected token ['
bash: /home/atlas/.bashrc: line 73:if [ -x /usr/bin/dircolors ] ; then '
I've tried to fix it using
"cp /ect/skel/.bashrc ~/"
And I get this "cp: cannot stat `/ect/skel/.bashrc': No such file or directory"
I'm unsure of why this is doing this and how to fix it.
Inxsible wrote:If you have your own ~/.bashrc, it will override your /etc/bash.bashrc file because ~/.bashrc is sourced after /etc/bash.bashrc and you won't see the changes you made in the /etc/bash.bashrc file.Thanks that's what I was looking for, appreciate it.
I'm running RHEL5. I added simple alias command into ~/.bashrc. When I start a new terminal, nothing happens but source ~/.bashrc works so I know the syntax is correct. I also modified/source-tested ~/.bash_profiles but it's not executed on terminal startup either.
Is there a simple way to list all the command conflicts that have occurred in the system due to the bashrc update involving alias commands?
For example, someone writes alias ls=/path/to/user-generated/executable in bashrc. How does one find out that this is masking an actual command (ls). One way seems to be to run all the aliases before and after sourcing bashrc and diff the output.