Find the answer to your Linux question:
Results 1 to 4 of 4
I'm having the following trouble: Code: bash etc/bashrc line 14 syntax error near unexpected token `in 'bash: /etc/bashrc: line 14: ` case $TERM in I just can't paste the contents ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2013
    Posts
    4

    bashrc syntax error near unexpected token `in case $TERM


    I'm having the following trouble:
    Code:
    bash etc/bashrc line 14 syntax error near unexpected token `in
    'bash: /etc/bashrc: line 14: ` case $TERM in
    I just can't paste the contents of the file as I receive an error in the forum

    The following errors occurred with your submission
    You are only allowed to post URLs (the ones giving the error) to other sites after you have made 15 posts or more.

    Also tried to upload but "Invalid file"

    So it is linux + bashrc + the forum, error, error

    Thanks

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,392
    hi and welcome

    try to copy&paste the /etc/bashrc in CODE tags
    You must always face the curtain with a bow.

  3. #3
    Just Joined!
    Join Date
    Mar 2013
    Posts
    4
    It worked now to use code for posting on the quick reply but didn't work when I tried to create the thread,
    Any easy errors to detect just by looking, thanks so much.
    Code:
    # /etc/bashrc
    
    # System wide functions and aliases
    # Environment stuff goes in /etc/profile
    
    # It's NOT a good idea to change this file unless you know what you
    # are doing. It's much better to create a custom.sh shell script in
    # /etc/profile.d/ to make custom changes to your environment, as this
    # will prevent the need for merging in future updates.
    
    # are we an interactive shell?
    if [ "$PS1" ]; then
      if [ -z "$PROMPT_COMMAND" ]; then
        case $TERM in
        xterm*)
            if [ -e /etc/sysconfig/bash-prompt-xterm ]; then
                PROMPT_COMMAND=/etc/sysconfig/bash-prompt-xterm
            else
                PROMPT_COMMAND='printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'
            fi
            ;;
        screen)
            if [ -e /etc/sysconfig/bash-prompt-screen ]; then
                PROMPT_COMMAND=/etc/sysconfig/bash-prompt-screen
            else
                PROMPT_COMMAND='printf "\033]0;%s@%s:%s\033\\" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'
            fi
            ;;
        *)
            [ -e /etc/sysconfig/bash-prompt-default ] && PROMPT_COMMAND=/etc/sysconfig/bash-prompt-default
            ;;
          esac
      fi
      # Turn on checkwinsize
      shopt -s checkwinsize
      [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ "
      # You might want to have e.g. tty in prompt (e.g. more virtual machines)
      # and console windows
      # If you want to do so, just add e.g.
      # if [ "$PS1" ]; then
      #   PS1="[\u@\h:\l \W]\\$ "
      # fi
      # to your custom modification shell script in /etc/profile.d/ directory
    fi
    
    if ! shopt -q login_shell ; then # We're not a login shell
        # Need to redefine pathmunge, it get's undefined at the end of /etc/profile
        pathmunge () {
            case ":${PATH}:" in
                *:"$1":*)
                    ;;
                *)
                    if [ "$2" = "after" ] ; then
                        PATH=$PATH:$1
                    else
                        PATH=$1:$PATH
                    fi
            esac
        }
    
        # By default, we want umask to get set. This sets it for non-login shell.
        # Current threshold for system reserved uid/gids is 200
        # You could check uidgid reservation validity in
        # /usr/share/doc/setup-*/uidgid file
        if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
           umask 002
        else
           umask 022
        fi
    
        # Only display echos from profile.d scripts if we are no login shell
        # and interactive - otherwise just process them to set envvars
        for i in /etc/profile.d/*.sh; do
            if [ -r "$i" ]; then
                if [ "$PS1" ]; then
                    . "$i"
                else
                    . "$i" >/dev/null 2>&1
                fi
            fi
        done
    
        unset i
        unset pathmunge
    fi
    # vim:ts=4:sw=4

  4. #4
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,392
    Your /etc/bashrc looks like the original one from the package, which is good.

    The following gives the package containing /etc/bashrc (should be "setup", IIRC)
    Code:
    rpm -qf /etc/bashrc
    Then verify this package (please replace "setup", if the previous query results in a different package)
    Code:
    rpm -V setup
    If /etc/bashrc is unmodified, then it is not the problem (at least it is very unlikely to be a problem).

    I would then look at that $TERM variable.
    How is it set for your user?
    You must always face the curtain with a bow.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •