![Bash 错误:查找匹配时出现意外的 EOF,语法错误:文件意外结束](https://linux22.com/image/945125/Bash%20%E9%94%99%E8%AF%AF%EF%BC%9A%E6%9F%A5%E6%89%BE%E5%8C%B9%E9%85%8D%E6%97%B6%E5%87%BA%E7%8E%B0%E6%84%8F%E5%A4%96%E7%9A%84%20EOF%EF%BC%8C%E8%AF%AD%E6%B3%95%E9%94%99%E8%AF%AF%EF%BC%9A%E6%96%87%E4%BB%B6%E6%84%8F%E5%A4%96%E7%BB%93%E6%9D%9F.png)
我用 ShellCheck 运行了它,但不明白它想让我改变什么,所以我来了。
打开终端:
bash: /home/helpabrother/.bashrc: line 118: unexpected EOF while looking for matching
“”
bash: /home/helpabrother/.bashrc: line 121: syntax error: unexpected end of file
我也很好奇这一行是做什么的。
'export PATH="echo export PATH="/home/mark/.local/bin:$PATH" >> ~/.bashrc && source ~/.bashrc:$PATH" '
.Bash文件:
# ~/.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|*-256color) 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
# 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
# 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 -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
# 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
export PATHn:$PATH"
export PATH=/home/helpabrother/.local/bin:$PATHexport PATHn:$PATH"
export PATH="echo export PATH="/home/mark/.local/bin:$PATH" >> ~/.bashrc && source ~/.bashrc:$PATH"
export PATHn:$PATH"
答案1
显然,您更改.bashrc
文件时对 bash 并不十分了解,甚至可能不知道自己真正想要实现什么。除非是恶意软件,否则程序不太可能做出这些笨拙的更改。存在语法错误。第 118 行缺少开头引号。第 121 行做了一件非常奇怪的事情,包括在名为 的文件中执行源操作~/.bashrc:$PATH
。
除非你非常清楚自己想要实现什么,否则最好的建议是:恢复你的默认 bashrc:
cp /etc/skel/.bashrc ~
然后你仍然可以了解你的需求是什么,如果不确定如何实现你想要的,可以提出一个具体的问题。
答案2
export
删除文件中以 开头的最后 5 行~/.bashrc
(如果我没记错的话是第 118-122 行) - 这是一个混乱。
然后阅读如何正确设置PATH
- 正常语法是:
export PATH="/my/new/path:$PATH"
如果您需要执行“嵌套”/“链式”加载的情况~/.bashrc
(例如使用屏幕或 tmux),您可以执行如下条件路径:
[[ $PATH != *"/my/new/path"* ]] && export PATH="/my/new/path:$PATH"
上述操作将确保/my/new/path
仅当其尚不存在时才会添加。
然后以正确的方式做~/.bashrc