答案 0 :(得分:18)
原因可能是修改后的bash_profile文件。 尝试将这些行添加到〜/ .bash_profile
source ~/.bashrc
或从终端运行命令
echo "source ~/.bashrc" >> ~/.bash_profile
答案 1 :(得分:1)
I ran into this forum hoping to find the solution to my problem. I eventually figured it out so here's how I fixed it:
Ctl
+ r
, typing bash
and pressing enter.cd ~
nano .bashrc
Delete everything in that file and replace it with this:
# ~/.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
Save the file with Ctl
+ o
Reload the terminal. Try executing . .bashrc
if it doesn't work. (notice the space between the two periods in that last command).
I don't know if the original poster will get this, but hopefully it will help a poor soul who stumbles upon it.
答案 2 :(得分:0)
我最近遇到了同样的问题;我的想法是MS更新了快捷方式,它以某种方式默认为没有颜色?我想我可能会记录是否有人偶然发现了这篇文章。
如果打开开始菜单,向下滚动到" Ubuntu",现在应该有两个项目:Ubuntu(带有完整的橙色图标)和Ubuntu终端(带有圆形规范徽标) 。 打开Ubuntu提供标准的彩色终端,而打开Ubuntu终端则提供纯灰色终端。
要修复,请更改快捷方式(之后应该没问题),或尝试wsltty
:
wsltty
- 它看起来很花哨,似乎支持在默认终端窗口上更好的复制/粘贴 - 可能是一个更好的选择答案 3 :(得分:0)
在您的.bashrc
中,尝试取消注释以下行以强制使用颜色:
#force_color_prompt=yes
答案 4 :(得分:0)
答案 5 :(得分:0)
您运行的 shell 可能与 bash 不同。其中一些看起来相同。我当前安装的 WSL Ubuntu 出于某种原因从 sh 开始。我就是这样解决的。
可以通过做检查
echo $SHELL
如果是 /bin/bash 以外的任何其他内容,如果您的 shell 在提示中显示您的用户名,您可以通过从 @ 之前获取您的用户名来更改它,在我的情况下是 cjohnson 并发出命令:sudo usermod -s /bin /bash cjohnson
如果您当前的 shell 没有在提示中列出您的用户名,您可以使用命令:whoami
-s flash 告诉 usermod 为最后列出的用户修改 shell。
然后当你打开一个新的 shell 时应该得到正常的 bash shell。
因为没有选择答案。认为这是离开它的最佳位置,因为这是我对此问题的第一个搜索结果。未显示 WSL 终端颜色。