Help if you would please - Printable Version

Help if you would please - Printable Version

+- Linux-Noob Forums (https://www.linux-noob.com/forums)
+-- Forum: Linux Noob (https://www.linux-noob.com/forums/forum-3.html)
+--- Forum: Just Starting Linux (https://www.linux-noob.com/forums/forum-63.html)
+--- Thread: Help if you would please (/thread-565.html)

Help if you would please - robbin - 2009-10-09

Hi again, I updated Ubuntu Ibex to Jaunty that's all good now but my terminal now has two lines above the, user@ubuntu:~$

I have not seen this at any other time, then again I know little about Linux apart from its called the hackers tool? and it runs the internet, right?

my terminal after opening

bash: /home/user/.bashrc: line 102: unexpected EOF while looking for matching `"'

bash: /home/user/.bashrc: line 103: syntax error: unexpected end of file

user@ubuntu:~$ any advice on what to do, thanks robbin itall

Help if you would please - znx - 2009-10-09

Quote:bash: /home/user/.bashrc: line 102: unexpected EOF while looking for matching `"'

bash: /home/user/.bashrc: line 103: syntax error: unexpected end of file

Help if you would please - robbin - 2009-10-09

Quote:<blockquote data-ipsquote="" class="ipsQuote" data-ipsquote-contentcommentid="13737" data-ipsquote-username="robbin" data-cite="robbin" data-ipsquote-timestamp="1255050273" data-ipsquote-contentapp="forums" data-ipsquote-contenttype="forums" data-ipsquote-contentid="3891" data-ipsquote-contentclass="forums_Topic"><div>
bash: /home/user/.bashrc: line 102: unexpected EOF while looking for matching `"'

bash: /home/user/.bashrc: line 103: syntax error: unexpected end of file

Linux isn't a hacker's tool any more than Windows is. Linux is an Operating System, which means it can be used for any purpose. If you upload a copy of your bashrc I will look at it and tell you what the problem is.

</div></blockquote>

Thanks for the reply, being Very new to this I know Very little about Linux and I learn as I go, so, gedit .bashrc

then this is the file mate.

# ~/.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

[ -z "$PS1" ] && return

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

# don't overwrite GNU Midnight Commander's setting of `ignorespace'.

export HISTCONTROL=$HISTCONTROL${HISTCONTROL+,}ignoredups

# ... or force ignoredups and ignorespace

export HISTCONTROL=ignoreboth

# 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

# 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)

fi

# set a fancy prompt (non-color, unless we know we "want" color)

case "$TERM" in

xterm-color) color_prompt=yes;;

esac

# 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

#force_color_prompt=yes

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.)

color_prompt=yes

else

color_prompt=

fi

fi

if [ "$color_prompt" = yes ]; then

PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '

else

PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '

fi

unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir

case "$TERM" in

xterm*|rxvt*)

PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"

;;

*)

;;

esac

# 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

#fi

# enable color support of ls and also add handy aliases

if [ -x /usr/bin/dircolors ]; then

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'

fi

# some more ls aliases

#alias ll='ls -l'

#alias la='ls -A'

#alias l='ls -CF'

# 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 [ -f /etc/bash_completion ]; then

. /etc/bash_completion

fi

###My Aliases

#open bashrc

alias ebrc="nano ~/.bashrc

And thanks again in advance.

Help if you would please - znx - 2009-10-10

There is a simple fix here, see at the very end of the bashrc:

Code:
###My Aliases

#open bashrc

alias ebrc="nano ~/.bashrc

You are missing the closing quote on that alias. SO it should be:

Code:
###My Aliases

#open bashrc

alias ebrc="nano ~/.bashrc"

Save and there will no longer be any complaints.

Help if you would please - robbin - 2009-10-10

Quote:There is a simple fix here, see at the very end of the bashrc:

Code:
###My Aliases #open bashrc alias ebrc="nano ~/.bashrc

<div>

You are missing the closing quote on that alias. SO it should be:

Code:
###My Aliases #open bashrc alias ebrc="nano ~/.bashrc"

Save and there will no longer be any complaints.

</div>

Thanks man I'm goner do it now and I mean thanks, later