Bash导出:不是有效的标识符

Bash导出:不是有效的标识符,bash,ls-colors,Bash,Ls Colors,我有一个树莓皮做的树莓皮。 默认情况下,shell以彩色格式显示自己,我想通过以下操作稍微更改这些设置,操作LS\u COLORS变量: LS_COLORS="ow=01;90:di=01;90" export LS_COLORS 当我通过ssh登录时会出现问题。在提示常规操作之前,它会显示以下内容: -bash: export: `LS_COLORS:': not a valid identifier 我已经在~/.bashrc和~/.bash_配置文件中查找过了(实际上这个配置文件不存在

我有一个树莓皮做的树莓皮。 默认情况下,shell以彩色格式显示自己,我想通过以下操作稍微更改这些设置,操作
LS\u COLORS
变量:

LS_COLORS="ow=01;90:di=01;90"
export LS_COLORS
当我通过ssh登录时会出现问题。在提示常规操作之前,它会显示以下内容:

-bash: export: `LS_COLORS:': not a valid identifier
我已经在
~/.bashrc
~/.bash_配置文件
中查找过了(实际上这个配置文件不存在)。 我没有在
.bashrc
中更改任何内容,也没有任何内容直接指向LS\u颜色。 我还尝试
$unset LS_COLORS
,但在下次登录时没有任何更改。 谢谢你的帮助

.bashrc
供参考:

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

# 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
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 [ -f /etc/bash_completion ] && ! shopt -oq posix; then
    . /etc/bash_completion
fi
这条线看起来可疑:

test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)":

确定要在下线使用冒号?

检查脚本中的DOS行结尾。我怀疑你实际上是在尝试导出
LS\u颜色\r
。你在某个地方有
LS\u颜色:
——你有一个共同的想法去哪里找?你可以在树莓PI上的主目录中运行
grep'LS\u颜色:'~/.
,试图找到报告的错误发生的地方。请发布
~/.bashrc
的内容这一行和整个
.bashrc
文件都是Raspbian附带的原始文件。我没有编辑任何这些。