[Bug] Can't code in terminal (corrupted ~/.bashrc file)

This is an error report.

Screenshot of the error

Error details


I can't code in the terminal, the user is not in green as previously

Why is there a "user@3 xterm:-~" instead

Please help me !

Thanks in advance

Hi @teodnl,

according to what I can see in the screenshot, it seems that you have accidentally modified the ~/.bashrc file.

The easiest way of solving this is the following:

  1. Create a file called ~/bashrc with:
touch ~/bashrc
  1. Open that file using the Code Editor and paste the following content to it:
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# ------------------------------------------------------------------------------
# When running commands through Python's Popen or Python's SSH Client (paramiko)
# the shells are not interactive and "source /home/user/.bash_aliases" is not
# executed. Because of that our scripts fails for not having ROS_* variables
# defined. Since we always need those variables, no matter whether we are using
# ssh or python, we uncomment the lines below.
# It is worth mentioning also that when running commands with
#   sudo su user -c "echo commands executed by the 'user' user"
# the ~/.bashrc is not called. In those cases we have to explicitly call
#   source ~/.bashrc
# More details on PR #122.
# ------------------------------------------------------------------------------
# # If not running interactively, don't do anything
# case $- in
#    *i*) ;;
#      *) return;;
# esac

# ------------------------------------------------------------------------------
# After we disabled the "return" above the course tests started failing because
# we have "set -e" and the /usr/share/bash-completion/bash_completion fails.
# Let's them disable the "set -e" if it is enabled.
# ------------------------------------------------------------------------------
if shopt -po errexit > /dev/null; then
    set +e
# ------------------------------------------------------------------------------

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
        # We have color support; assume it's compliant with Ecma-48
        # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
        # a case would tend to support setf rather than setaf.)

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

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

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion

# If we from The Construct disabled "set -e", let's enable it again.
if  [[ "${tc__exit_on_error}" == "true" ]]; then set -e; fi
unset tc__exit_on_error

# -----------------------------------------------------
#           Note from The Construct
# -----------------------------------------------------
# This file will be saved together with your rosject.
# Add your custom exports at the end of this file. E.g.:
#   export MY_SETTING=value
#   export GAZEBO_RESOURCE_PATH=$GAZEBO_RESOURCE_PATH:/home/user/simulation_ws/src/my_package
# -----------------------------------------------------

  1. Now, using the terminal, rename the bashrc file to .bashrc:
mv ~/bashrc ~/.bashrc
  1. Now, source that file in each terminal and you should be good to go:
source ~/.bashrc

Now everything should work as expected.

Please let us know if you still have any issues.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.