unexpected end of file bashrcScrewed up my .bashrc fileCommands not working after editing .bashrc...

Can an Area of Effect spell cast outside a Prismatic Wall extend inside it?

Alignment of various blocks in tikz

Like totally amazing interchangeable sister outfits II: The Revenge

Does a large simulator bay have standard public address announcements?

Contradiction proof for inequality of P and NP?

Critique of timeline aesthetic

How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?

Implications of cigar-shaped bodies having rings?

How do I reattach a shelf to the wall when it ripped out of the wall?

How do I check if a string is entirely made of the same substring?

How come there are so many candidates for the 2020 Democratic party presidential nomination?

Two field separators (colon and space) in awk

Function pointer with named arguments?

What is the most expensive material in the world that could be used to create Pun-Pun's lute?

How to denote matrix elements succinctly?

Do I have an "anti-research" personality?

A strange hotel

Providing evidence of Consent of Parents for Marriage by minor in England in early 1800s?

Why does Mind Blank stop the Feeblemind spell?

Is it idiomatic to construct against `this`

On The Origin of Dissonant Chords

Pulling the rope with one hand is as heavy as with two hands?

How could Tony Stark make this in Endgame?

Pre-plastic human skin alternative



unexpected end of file bashrc


Screwed up my .bashrc fileCommands not working after editing .bashrc fileUnexpected end of fileSyntax Error: Unexpected end of fileCan't access hidden bashrc filebash: syntax error: unexpected end of fileSyntax error: end of file unexpectedAWK syntax error: unexpected end of fileLine 17 Syntax error: unexpected end of filesyntax error near unexpected token `newline' in .bashrc






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







3















When I open a terminal, I get:



line 106 unexpected EOF while looking for matching `''
line 120 syntax error: unexpected end of file


bashrc has



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

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
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)
HISTSIZE=1000
HISTFILESIZE=2000

# 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)
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)}[33[01;32m]u@h
[33[00m]:[33[01;34m]w[33[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: wa]$PS1"
;;
*)
;;
esac

# 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'
fi

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

# enable programmable completion features (you don't need to enable
#line 106 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
fi
fi

JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
export JAVA_HOME
PATH=$PATH:$JAVA_HOME/bin
export PATH


There is no line 120! The last line I have is 119 .
I tried to figure out where the problem was but I couldn't find anything.










share|improve this question

























  • Are those `s remnants from formatting?

    – heemayl
    Apr 15 '17 at 13:41











  • sorry , I deleted it

    – user3188912
    Apr 15 '17 at 13:43






  • 1





    Ok, please add your full ~/.bashrc

    – heemayl
    Apr 15 '17 at 13:44






  • 1





    What is the line 106 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile line? Is that actually in your file? Do you have the words line 106 there as you show?

    – terdon
    Apr 15 '17 at 13:46






  • 2





    For those types of error you may use shellcheck.net Copy and paste your code and it points you directly to those errors (beside a lot of improvement tipps).

    – ULick
    Apr 15 '17 at 17:32


















3















When I open a terminal, I get:



line 106 unexpected EOF while looking for matching `''
line 120 syntax error: unexpected end of file


bashrc has



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

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
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)
HISTSIZE=1000
HISTFILESIZE=2000

# 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)
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)}[33[01;32m]u@h
[33[00m]:[33[01;34m]w[33[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: wa]$PS1"
;;
*)
;;
esac

# 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'
fi

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

# enable programmable completion features (you don't need to enable
#line 106 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
fi
fi

JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
export JAVA_HOME
PATH=$PATH:$JAVA_HOME/bin
export PATH


There is no line 120! The last line I have is 119 .
I tried to figure out where the problem was but I couldn't find anything.










share|improve this question

























  • Are those `s remnants from formatting?

    – heemayl
    Apr 15 '17 at 13:41











  • sorry , I deleted it

    – user3188912
    Apr 15 '17 at 13:43






  • 1





    Ok, please add your full ~/.bashrc

    – heemayl
    Apr 15 '17 at 13:44






  • 1





    What is the line 106 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile line? Is that actually in your file? Do you have the words line 106 there as you show?

    – terdon
    Apr 15 '17 at 13:46






  • 2





    For those types of error you may use shellcheck.net Copy and paste your code and it points you directly to those errors (beside a lot of improvement tipps).

    – ULick
    Apr 15 '17 at 17:32














3












3








3








When I open a terminal, I get:



line 106 unexpected EOF while looking for matching `''
line 120 syntax error: unexpected end of file


bashrc has



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

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
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)
HISTSIZE=1000
HISTFILESIZE=2000

# 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)
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)}[33[01;32m]u@h
[33[00m]:[33[01;34m]w[33[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: wa]$PS1"
;;
*)
;;
esac

# 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'
fi

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

# enable programmable completion features (you don't need to enable
#line 106 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
fi
fi

JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
export JAVA_HOME
PATH=$PATH:$JAVA_HOME/bin
export PATH


There is no line 120! The last line I have is 119 .
I tried to figure out where the problem was but I couldn't find anything.










share|improve this question
















When I open a terminal, I get:



line 106 unexpected EOF while looking for matching `''
line 120 syntax error: unexpected end of file


bashrc has



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

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
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)
HISTSIZE=1000
HISTFILESIZE=2000

# 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)
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)}[33[01;32m]u@h
[33[00m]:[33[01;34m]w[33[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: wa]$PS1"
;;
*)
;;
esac

# 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'
fi

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

# enable programmable completion features (you don't need to enable
#line 106 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
fi
fi

JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
export JAVA_HOME
PATH=$PATH:$JAVA_HOME/bin
export PATH


There is no line 120! The last line I have is 119 .
I tried to figure out where the problem was but I couldn't find anything.







command-line bash bashrc






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 15 '17 at 14:07









muru

1




1










asked Apr 15 '17 at 13:29









user3188912user3188912

1471210




1471210













  • Are those `s remnants from formatting?

    – heemayl
    Apr 15 '17 at 13:41











  • sorry , I deleted it

    – user3188912
    Apr 15 '17 at 13:43






  • 1





    Ok, please add your full ~/.bashrc

    – heemayl
    Apr 15 '17 at 13:44






  • 1





    What is the line 106 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile line? Is that actually in your file? Do you have the words line 106 there as you show?

    – terdon
    Apr 15 '17 at 13:46






  • 2





    For those types of error you may use shellcheck.net Copy and paste your code and it points you directly to those errors (beside a lot of improvement tipps).

    – ULick
    Apr 15 '17 at 17:32



















  • Are those `s remnants from formatting?

    – heemayl
    Apr 15 '17 at 13:41











  • sorry , I deleted it

    – user3188912
    Apr 15 '17 at 13:43






  • 1





    Ok, please add your full ~/.bashrc

    – heemayl
    Apr 15 '17 at 13:44






  • 1





    What is the line 106 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile line? Is that actually in your file? Do you have the words line 106 there as you show?

    – terdon
    Apr 15 '17 at 13:46






  • 2





    For those types of error you may use shellcheck.net Copy and paste your code and it points you directly to those errors (beside a lot of improvement tipps).

    – ULick
    Apr 15 '17 at 17:32

















Are those `s remnants from formatting?

– heemayl
Apr 15 '17 at 13:41





Are those `s remnants from formatting?

– heemayl
Apr 15 '17 at 13:41













sorry , I deleted it

– user3188912
Apr 15 '17 at 13:43





sorry , I deleted it

– user3188912
Apr 15 '17 at 13:43




1




1





Ok, please add your full ~/.bashrc

– heemayl
Apr 15 '17 at 13:44





Ok, please add your full ~/.bashrc

– heemayl
Apr 15 '17 at 13:44




1




1





What is the line 106 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile line? Is that actually in your file? Do you have the words line 106 there as you show?

– terdon
Apr 15 '17 at 13:46





What is the line 106 # this, if it's already enabled in /etc/bash.bashrc and /etc/profile line? Is that actually in your file? Do you have the words line 106 there as you show?

– terdon
Apr 15 '17 at 13:46




2




2





For those types of error you may use shellcheck.net Copy and paste your code and it points you directly to those errors (beside a lot of improvement tipps).

– ULick
Apr 15 '17 at 17:32





For those types of error you may use shellcheck.net Copy and paste your code and it points you directly to those errors (beside a lot of improvement tipps).

– ULick
Apr 15 '17 at 17:32










1 Answer
1






active

oldest

votes


















8














Your problem is line 93:



alias ll='ls -alF


You're missing the closing quote ('). That should be:



alias ll='ls -alF'


The error you are getting is confusing because bash sees the opening ' and then tries to find a closing one, and that confuses its parser completely. Just fix the missing ' there and you should be fine.



It is complaining about line 120 because it searches all the way to the end of the file (so last line + 1) and doesn't find its closing quote.






share|improve this answer
























  • yes, that's right . thanks, really i'm on this problem for a week searching !

    – user3188912
    Apr 15 '17 at 14:08








  • 1





    This and the coloring helps in pinpointing the problem

    – Rinzwind
    Apr 15 '17 at 14:08











  • @Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

    – terdon
    Apr 15 '17 at 14:10












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f905113%2funexpected-end-of-file-bashrc%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









8














Your problem is line 93:



alias ll='ls -alF


You're missing the closing quote ('). That should be:



alias ll='ls -alF'


The error you are getting is confusing because bash sees the opening ' and then tries to find a closing one, and that confuses its parser completely. Just fix the missing ' there and you should be fine.



It is complaining about line 120 because it searches all the way to the end of the file (so last line + 1) and doesn't find its closing quote.






share|improve this answer
























  • yes, that's right . thanks, really i'm on this problem for a week searching !

    – user3188912
    Apr 15 '17 at 14:08








  • 1





    This and the coloring helps in pinpointing the problem

    – Rinzwind
    Apr 15 '17 at 14:08











  • @Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

    – terdon
    Apr 15 '17 at 14:10
















8














Your problem is line 93:



alias ll='ls -alF


You're missing the closing quote ('). That should be:



alias ll='ls -alF'


The error you are getting is confusing because bash sees the opening ' and then tries to find a closing one, and that confuses its parser completely. Just fix the missing ' there and you should be fine.



It is complaining about line 120 because it searches all the way to the end of the file (so last line + 1) and doesn't find its closing quote.






share|improve this answer
























  • yes, that's right . thanks, really i'm on this problem for a week searching !

    – user3188912
    Apr 15 '17 at 14:08








  • 1





    This and the coloring helps in pinpointing the problem

    – Rinzwind
    Apr 15 '17 at 14:08











  • @Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

    – terdon
    Apr 15 '17 at 14:10














8












8








8







Your problem is line 93:



alias ll='ls -alF


You're missing the closing quote ('). That should be:



alias ll='ls -alF'


The error you are getting is confusing because bash sees the opening ' and then tries to find a closing one, and that confuses its parser completely. Just fix the missing ' there and you should be fine.



It is complaining about line 120 because it searches all the way to the end of the file (so last line + 1) and doesn't find its closing quote.






share|improve this answer













Your problem is line 93:



alias ll='ls -alF


You're missing the closing quote ('). That should be:



alias ll='ls -alF'


The error you are getting is confusing because bash sees the opening ' and then tries to find a closing one, and that confuses its parser completely. Just fix the missing ' there and you should be fine.



It is complaining about line 120 because it searches all the way to the end of the file (so last line + 1) and doesn't find its closing quote.







share|improve this answer












share|improve this answer



share|improve this answer










answered Apr 15 '17 at 14:05









terdonterdon

68.1k13141225




68.1k13141225













  • yes, that's right . thanks, really i'm on this problem for a week searching !

    – user3188912
    Apr 15 '17 at 14:08








  • 1





    This and the coloring helps in pinpointing the problem

    – Rinzwind
    Apr 15 '17 at 14:08











  • @Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

    – terdon
    Apr 15 '17 at 14:10



















  • yes, that's right . thanks, really i'm on this problem for a week searching !

    – user3188912
    Apr 15 '17 at 14:08








  • 1





    This and the coloring helps in pinpointing the problem

    – Rinzwind
    Apr 15 '17 at 14:08











  • @Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

    – terdon
    Apr 15 '17 at 14:10

















yes, that's right . thanks, really i'm on this problem for a week searching !

– user3188912
Apr 15 '17 at 14:08







yes, that's right . thanks, really i'm on this problem for a week searching !

– user3188912
Apr 15 '17 at 14:08






1




1





This and the coloring helps in pinpointing the problem

– Rinzwind
Apr 15 '17 at 14:08





This and the coloring helps in pinpointing the problem

– Rinzwind
Apr 15 '17 at 14:08













@Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

– terdon
Apr 15 '17 at 14:10





@Rinzwind yeah, since the OP hadn't tagged with bash, there was no coloring.

– terdon
Apr 15 '17 at 14:10


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f905113%2funexpected-end-of-file-bashrc%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

Simple Scan not detecting my scanner (Brother DCP-7055W)Brother MFC-L2700DW printer can print, can't...