.bashrc irritation ?

If none of the more specific forums is the right place to ask

.bashrc irritation ?

Postby Jethro_UK » 2019-08-14 15:10

I was trying to change my ssh/terminal settings to show a coloured prompt (useful when you have more than one server).

However, something in the .bashrc I created is now messing up the terminals linewrapping, so that it's pretty unreadable beyond 20 characters. Also the path which should show in the command prompt isn't wrapping.

renaming .bashrc fixes it. so I know where the issue is.

Anyone advise what I have done wrong - the problem occurs locally and via SSH ?

Code: Select all
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;

# 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|*-256color) 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'

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

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

# 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

#Make prompt colored when logged in remote
export NON_LOCAL_LOGIN=`env | grep SSH`
if [ "$NON_LOCAL_LOGIN" != "" ]; then
       PS1="\033[33m[\u@\h:\w]#\033[0m "
Posts: 24
Joined: 2014-08-12 09:31

Re: .bashrc irritation ?

Postby tynman » 2019-08-14 16:21

One thing I noticed: the last if statement lacks a matching fi statement.
Posts: 124
Joined: 2016-05-03 19:48
Location: British Columbia, Canada

Re: .bashrc irritation ?

Postby Jethro_UK » 2019-08-14 17:02

tynman wrote:One thing I noticed: the last if statement lacks a matching fi statement.

Sloppy cut and pasting - there is a matching fi statement.
Posts: 24
Joined: 2014-08-12 09:31

Re: .bashrc irritation ?

Postby phenest » 2019-08-14 17:28

I've just pasted that into my .bashrc and it works fine (apart from the missing "fi").

Is there something that I need to type or do in a terminal that causes the issue?
ASRock H77 Pro4-M i7 3770K - 32GB RAM - Pioneer BDR-209D
User avatar
Posts: 1704
Joined: 2010-03-09 09:38
Location: The Matrix

Re: .bashrc irritation ?

Postby L_V » 2019-08-14 17:50

Try to replace
Code: Select all
if [ "$NON_LOCAL_LOGIN" != "" ]; then
Code: Select all
if [ ! -z "$NON_LOCAL_LOGIN" ] ; then

or if .../...fi by
Code: Select all
 [ -z "$NON_LOCAL_LOGIN" ]  ||  PS1="\033[33m[\u@\h:\w]#\033[0m "
Posts: 1270
Joined: 2007-03-19 09:04

Return to General Questions

Who is online

Users browsing this forum: No registered users and 10 guests