document/TranslateProject
2
0
Fork 0
mirror of https://github.com/LCTT/TranslateProject.git synced 2025-01-13 22:30:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #15348 from wxy/20190906-How-to-change-the-color-of-your-Linux-terminal

Browse Source 
TSL&PRF:20190906 How to change the color of your Linux terminal
This commit is contained in:
Xingyu.Wang 2019-09-10 11:06:18 +08:00 committed by GitHub
commit 70e08d85f3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 200 additions and 211 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

211
sources/tech/20190906 How to change the color of your Linux terminal.md
View File

@ -1,211 +0,0 @@
[#]: collector: (lujun9972)
[#]: translator: (wxy)
[#]: reviewer: ( )
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (How to change the color of your Linux terminal)
[#]: via: (https://opensource.com/article/19/9/linux-terminal-colors)
[#]: author: (Seth Kenlon https://opensource.com/users/sethhttps://opensource.com/users/jason-bakerhttps://opensource.com/users/tlaihttps://opensource.com/users/amjithhttps://opensource.com/users/greg-phttps://opensource.com/users/marcobravo)
How to change the color of your Linux terminal
======
Make Linux as colorful (or as monochromatic) as you want.
![4 different color terminal windows with code][1]
You can add color to your Linux terminal using special ANSI encoding settings, either dynamically in a terminal command or in configuration files, or you can use ready-made themes in your terminal emulator. Either way, the nostalgic green or amber text on a black screen is wholly optional. This article demonstrates how you can make Linux as colorful (or as monochromatic) as you want.
### Terminal capabilities
Modern systems usually default to at least xterm-256color, but if you try to add color to your terminal without success, you should check your TERM setting.
Historically, Unix terminals were literally that: physical points at the literal endpoint (termination) of a shared computer system where users could type in commands. They were unique from the teletype machines (which is why we still have /dev/tty devices in Linux today) that were often used to issue commands remotely. Terminals had CRT monitors built-in, so users could sit at a terminal in their office to interact directly with the mainframe. CRT monitors were expensive—both to manufacture and to control; it was easier to have a computer spit out crude ASCII text than to worry about anti-aliasing and other niceties that modern computerists take for granted. However, developments in technology happened fast even then, and it quickly became apparent that as new video display terminals were designed, they needed new capabilities to be available on an optional basis.
For instance, the fancy new VT100 released in 1978 supported ANSI color, so if a user identified the terminal type as vt100, then a computer could deliver color output, while a basic serial device might not have such an option. The same principle applies today, and it's set by the TERM [environment variable][2]. You can check your TERM definition with **echo**:
```
$ echo $TERM
xterm-256color
```
The obsolete (but still maintained on some systems in the interest of backward compatibility) /etc/termcap file defined the capabilities of terminals and printers. The modern version of that is terminfo, located in either /etc or /usr/share, depending on your distribution. These files list features available in different kinds of terminals, many of which are defined by historical hardware: there are definitions for vt100 through vt220, as well as for modern software emulators like xterm and Xfce. Most software doesn't care what terminal type you're using; in rare instances, you might get a warning or error about an incorrect terminal type when logging into a server that checks for compatible features. If your terminal is set to a profile with very few features, but you know the emulator you use is capable of more, then you can change your setting by defining the TERM environment variable. You can do this by exporting the TERM variable in your ~/.bashrc configuration file:
```
`export TERM=xterm-256color`
```
Save the file, and reload your settings:
```
`$ source ~/.bashrc`
```
### ANSI color codes
Modern terminals have inherited ANSI escape sequences for "meta" features. These are special sequences of characters that a terminal interprets as actions instead of characters. For instance, this sequence clears the screen up to the next prompt:
```
`$ printf `\033[2J``
```
It doesn't clear your history; it just clears up the screen in your terminal emulator, so it's a safe and demonstrative ANSI escape sequence.
ANSI also has sequences to set the color of your terminal. For example, typing this code changes the subsequent text to green:
```
`$ printf '\033[32m'`
```
As long as you see color the same way your computer does, you could use color to help you remember what system you're logged into. For example, if you regularly SSH into your server, you can set your server prompt to green to help you differentiate it at a glance from your local prompt. For a green prompt, use the ANSI code for green before your prompt character and end it with the code representing your normal default color:
```
`export PS1=`printf "\033[32m$ \033[39m"``
```
### Foreground and background
You're not limited to setting the color of your text. With ANSI codes, you can control the background color of your text as well as do some rudimentary styling.
For instance, with **\033[4m**, you can cause text to be underlined, or with **\033[5m** you can set it to blink. That might seem silly at first—because you're probably not going to set your terminal to underline all text and blink all day—but it can be useful for select functions. For instance, you might set an urgent error produced by a shell script to blink (as an alert for your user), or you might underline a URL.
For your reference, here are the foreground and background color codes. Foreground colors are in the 30 range, while background colors are in the 40 range:
Color | Foreground | Background
---|---|---
Black | \033[30m | \033[40m
Red | \033[31m | \033[41m
Green | \033[32m | \033[42m
Orange | \033[33m | \033[43m
Blue | \033[34m | \033[44m
Magenta | \033[35m | \033[45m
Cyan | \033[36m | \033[46m
Light gray | \033[37m | \033[47m
Fallback to distro's default | \033[39m | \033[49m
There are some additional colors available for the background:
Color | Background
---|---
Dark gray | \033[100m
Light red | \033[101m
Light green | \033[102m
Yellow | \033[103m
Light blue | \033[104m
Light purple | \033[105m
Teal | \033[106m
White | \033[107m
### Permanency
Setting colors in your terminal session is only temporary and relatively unconditional. Sometimes the effect lasts for a few lines; that's because this method of setting colors relies on a printf statement to set a mode that lasts only until something else overrides it.
The way a terminal emulator typically gets instructions on what colors to use is from the settings of the LS_COLORS environment variable, which is in turn populated by the settings of dircolors. You can view your current settings with an echo statement:
```
$ echo $LS_COLORS
rs=0:di=38;5;33:ln=38;5;51:mh=00:pi=40;
38;5;11:so=38;5;13:do=38;5;5:bd=48;5;
232;38;5;11:cd=48;5;232;38;5;3:or=48;
5;232;38;5;9:mi=01;05;37;41:su=48;5;
196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;
196;38;5;226:tw=48;5;10;38;5;16:ow=48;5;
[...]
```
Or you can use dircolors directly:
```
$ dircolors --print-database
[...]
# image formats
.jpg 01;35
.jpeg 01;35
.mjpg 01;35
.mjpeg 01;35
.gif 01;35
.bmp 01;35
.pbm 01;35
.tif 01;35
.tiff 01;35
[...]
```
If that looks cryptic, it's because it is. The first digit after a file type is the attribute code, and it has six options:
* 00 none
* 01 bold
* 04 underscore
* 05 blink
* 07 reverse
* 08 concealed
The next digit is the color code in a simplified form. You can get the color code by taking the final digit of the ANSII code (32 for green foreground, 42 for green background; 31 or 41 for red, and so on).
Your distribution probably sets LS_COLORS globally, so all users on your system inherit the same colors. If you want a customized set of colors, you can use dircolors for that. First, generate a local copy of your color settings:
```
`$ dircolors --print-database > ~/.dircolors`
```
Edit your local list as desired. When you're happy with your choices, save the file. Your color settings are just a database and can't be used directly by [ls][3], but you can use dircolors to get shellcode you can use to set LS_COLORS:
```
$ dircolors --bourne-shell ~/.dircolors
LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:
pi=40;33:so=01;35:do=01;35:bd=40;33;01:
cd=40;33;01:or=40;31;01:mi=00:su=37;41:
sg=30;43:ca=30;41:tw=30;42:ow=34;
[...]
export LS_COLORS
```
Copy and paste that output into your ~/.bashrc file and reload. Alternatively, you can dump that output straight into your .bashrc file and reload.
```
$ dircolors --bourne-shell ~/.dircolors >> ~/.bashrc
$ source ~/.bashrc
```
You can also make Bash resolve .dircolors upon launch instead of doing the conversion manually. Realistically, you're probably not going to change colors often, so this may be overly aggressive, but it's an option if you plan on changing your color scheme a lot. In your .bashrc file, add this rule:
```
`[[ -e $HOME/.dircolors ]] && eval "`dircolors --sh $HOME/.dircolors`"`
```
Should you have a .dircolors file in your home directory, Bash evaluates it upon launch and sets LS_COLORS accordingly.
### Color
Colors in your terminal are an easy way to give yourself a quick visual reference for specific information. However, you might not want to lean on them too heavily. After all, colors aren't universal, so if someone else uses your system, they may not see the colors the same way you do. Furthermore, if you use a variety of tools to interact with computers, you might also find that some terminals or remote connections don't provide the colors you expect (or colors at all).
Those warnings aside, colors can be useful and fun in some workflows, so create a .dircolor database and customize it to your heart's content.
--------------------------------------------------------------------------------
via: https://opensource.com/article/19/9/linux-terminal-colors
作者：[Seth Kenlon][a]
选题：[lujun9972][b]
译者：[译者ID](https://github.com/译者ID)
校对：[校对者ID](https://github.com/校对者ID)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/sethhttps://opensource.com/users/jason-bakerhttps://opensource.com/users/tlaihttps://opensource.com/users/amjithhttps://opensource.com/users/greg-phttps://opensource.com/users/marcobravo
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/freedos.png?itok=aOBLy7Ky (4 different color terminal windows with code)
[2]: https://opensource.com/article/19/8/what-are-environment-variables
[3]: https://opensource.com/article/19/7/master-ls-command

200
translated/tech/20190906 How to change the color of your Linux terminal.md Normal file
View File

@ -0,0 +1,200 @@
[#]: collector: (lujun9972)
[#]: translator: (wxy)
[#]: reviewer: (wxy)
[#]: publisher: ( )
[#]: url: ( )
[#]: subject: (How to change the color of your Linux terminal)
[#]: via: (https://opensource.com/article/19/9/linux-terminal-colors)
[#]: author: (Seth Kenlon https://opensource.com/users/seth)
如何改变你的终端颜色
======
> 使 Linux 变得丰富多彩（或单色）。
![4 different color terminal windows with code][1]
你可以使用特殊的 ANSI 编码设置为 Linux 终端添加颜色，可以在终端命令或配置文件中动态添加，也可以在终端仿真器中使用现成的主题。无论哪种方式，你都可以黑色屏幕上找回怀旧的绿色或琥珀色文本。本文演示了如何使 Linux 变得丰富多彩（或单色）的方法。
### 终端的功能特性
现代系统的终端的颜色配置通常默认至少是 xterm-256color，但如果你尝试为终端添加颜色但未成功，则应检查你的 `TERM` 设置。
从历史上看，Unix 终端从字面上讲是：用户可以输入命令的共享计算机系统上实际的物理端点（终点）。它们专指通常用于远程发出命令的电传打字机（这也是我们今天在 Linux 中仍然使用 `/dev/tty` 设备的原因）。终端内置了 CRT 显示器，因此用户可以坐在办公室的终端上直接与大型机进行交互。CRT 显示器价格昂贵 —— 无论是制造还是使用控制；比担心抗锯齿和现代计算机专家理所当然认为的漂亮信息，让计算机吐出原始 ASCII 文本更容易。然而，即使在那时，技术的发展也很快，很快人们就会发现，随着新的视频显示终端的设计，他们需要新的功能特性来提供可选功能。
例如，1978 年发布的花哨的新 VT100 支持 ANSI 颜色，因此如果用户将终端类型识别为 vt100，则计算机可以提供彩色输出，而基本串行设备可能没有这样的选项。同样的原则适用于今天，它是由 `TERM` [环境变量][2]设定的。你可以使用 `echo` 检查你的 `TERM` 定义：
```
$ echo $TERM
xterm-256color
```
过时的（但在一些系统上仍然为了向后兼容而维护）`/etc/termcap` 文件定义了终端和打印机的功能特性。现代的版本是 `terminfo`，位于 `/etc` 或 `/usr/share` 中，具体取决于你的发行版。 这些文件列出了不同类型终端中可用的功能特性，其中许多都是由历史上的硬件定义的，如 vt100 到 vt220 的定义，以及 xterm 和 Xfce 等现代软件仿真器。大多数软件并不关心你使用的终端类型； 在极少数情况下，登录到检查兼容功能的服务器时，你可能会收到有关错误的终端类型的警告或错误。如果你的终端设置为功能特性很少的配置文件，但你知道你所使用的仿真器能够支持更多功能特性，那么你可以通过定义 `TERM` 环境变量来更改你的设置。你可以通过在 `~/.bashrc` 配置文件中导出 `TERM` 变量来完成此操作：
```
export TERM=xterm-256color
```
保存文件并重新载入设置：
```
$ source ~/.bashrc
```
### ANSI 颜色代码
现代终端继承了用于“元”特征的 ANSI 转义序列。这些是特殊的字符序列，终端将其解释为操作而不是字符。例如，此序列将清除屏幕，直到下一个提示符：
```
$ printf '\033[2J'
```
它不会清除你的历史信息；它只是清除终端仿真器中的屏幕，因此它是一个安全且具有示范性的 ANSI 转义序列。
ANSI 还具有设置终端颜色的序列。例如，键入此代码会将后续文本更改为绿色：
```
$ printf '\033[32m'
```
只要你对相同的计算机使用同一个颜色，就可以使用颜色来帮助你记住你登录的系统。例如，如果你经常通过 SSH 连接到服务器，则可以将服务器的提示符设置为绿色，以帮助你一目了然地将其与本地的提示符区分开来。 要设置绿色提示符，请在提示符前使用 ANSI 代码设置为绿色，并使用代表正常默认颜色的代码结束：
```
export PS1=`printf "\033[32m$ \033[39m"`
```
### 前景色和背景色
你不仅可以设置文本的颜色。使用 ANSI 代码，你还可以控制文本的背景颜色以及做一些基本的样式。
例如，使用 `\033[4m`，你可以为文本加上下划线，或者使用 `\033[5m` 你可以将其设置为闪烁的文本。起初这可能看起来很愚蠢，因为你可能不会将你的终端设置为所有文本带有下划线并整天闪烁， 但它对某些功能很有用。例如，你可以将 shell 脚本生成的紧急错误设置为闪烁（作为对用户的警报），或者你可以为 URL 添加下划线。
作为参考，以下是前景色和背景色的代码。前景色在 30 范围内，而背景色在 40 范围内：
颜色 | 前景色 | 背景色
---|---|---
黑色 | \033[30m | \033[40m
红色 | \033[31m | \033[41m
绿色 | \033[32m | \033[42m
橙色 | \033[33m | \033[43m
蓝色 | \033[34m | \033[44m
品红 | \033[35m | \033[45m
青色 | \033[36m | \033[46m
浅灰 | \033[37m | \033[47m
回退到发行版默认值 | \033[39m | \033[49m
还有一些可用于背景的其他颜色：
颜色 | 背景色
---|---
深灰 | \033[100m
浅红 | \033[101m
浅绿 | \033[102m
黄色 | \033[103m
浅蓝 | \033[104m
浅紫 | \033[105m
蓝绿 | \033[106m
白色 | \033[107m
### 持久设置
在终端会话中设置颜色只是暂时的，相对无条件的。有时效果会持续几行；这是因为这种设置颜色的方法依赖于 `printf` 语句来设置一种模式，该模式仅持续到其他设置覆盖它。
终端仿真器通常获取使用哪种颜色的指令的方式来自于 `LS_COLORS` 环境变量的设置，该设置又由 `dircolors` 的设置填充。你可以使用 `echo` 语句查看当前设置：
```
$ echo $LS_COLORS
rs=0:di=38;5;33:ln=38;5;51:mh=00:pi=40;
38;5;11:so=38;5;13:do=38;5;5:bd=48;5;
232;38;5;11:cd=48;5;232;38;5;3:or=48;
5;232;38;5;9:mi=01;05;37;41:su=48;5;
196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;
196;38;5;226:tw=48;5;10;38;5;16:ow=48;5;
[...]
```
或者你可以直接使用 `dircolors`：
```
$ dircolors --print-database
[...]
# image formats
.jpg 01;35
.jpeg 01;35
.mjpg 01;35
.mjpeg 01;35
.gif 01;35
.bmp 01;35
.pbm 01;35
.tif 01;35
.tiff 01;35
[...]
```
这看起来很神秘。文件类型后面的第一个数字是属性代码，它有六种选择：
* 00 无
* 01 粗体
* 04 下划线
* 05 闪烁
* 07 反白
* 08 暗色
下一个数字是简化形式的颜色代码。你可以通过获取 ANSI 代码的最后一个数字来获取颜色代码（绿色前景为 32，绿色背景为 42；红色为 31 或 41，依此类推）。
你的发行版可能全局设置了 `LS_COLORS`，因此系统上的所有用户都会继承相同的颜色。如果你想要一组自定义的颜色，可以使用 `dircolors`。首先，生成颜色设置的本地副本：
```
$ dircolors --print-database > ~/.dircolors
```
根据需要编辑本地列表。如果你对自己的选择感到满意，请保存文件。你的颜色设置只是一个数据库，不能由 [ls][3] 直接使用，但你可以使用 `dircolors` 获取可用于设置 `LS_COLORS` 的 shellcode：
```
$ dircolors --bourne-shell ~/.dircolors
LS_COLORS='rs=0:di=01;34:ln=01;36:mh=00:
pi=40;33:so=01;35:do=01;35:bd=40;33;01:
cd=40;33;01:or=40;31;01:mi=00:su=37;41:
sg=30;43:ca=30;41:tw=30;42:ow=34;
[...]
export LS_COLORS
```
将输出复制并粘贴到 `~/.bashrc` 文件中并重新加载。或者，你可以将该输出直接转储到 `.bashrc` 文件中并重新加载。
```
$ dircolors --bourne-shell ~/.dircolors >> ~/.bashrc
$ source ~/.bashrc
```
你也可以在启动时使 Bash 解析 `.dircolors` 而不是手动进行转换。实际上，你可能不会经常改变颜色，所以这可能过于激进，但如果你打算改变你的配色方案，这是一个选择。在 `.bashrc` 文件中，添加以下规则：
```
[[ -e $HOME/.dircolors ]] && eval "`dircolors --sh $HOME/.dircolors`"
```
如果你的主目录中有 `.dircolors` 文件，Bash 会在启动时对其进行评估并相应地设置 `LS_COLORS`。
### 颜色
在终端中使用颜色是一种可以为你自己提供特定信息的快速视觉参考的简单方法。但是，你可能不希望过于依赖它们。毕竟，颜色不是通用的，所以如果其他人使用你的系统，他们可能不会像你那样看懂颜色代表的含义。此外，如果你使用各种工具与计算机进行交互，你可能还会发现某些终端或远程连接无法提供你期望的颜色（或根本不提供颜色）。
除了上述警示之外，颜色在某些工作流程中可能很有用且很有趣，因此创建一个 `.dircolor` 数据库并根据你的想法对其进行自定义吧。
--------------------------------------------------------------------------------
via: https://opensource.com/article/19/9/linux-terminal-colors
作者：[Seth Kenlon][a]
选题：[lujun9972][b]
译者：[wxy](https://github.com/wxy)
校对：[wxy](https://github.com/wxy)
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
[a]: https://opensource.com/users/seth
[b]: https://github.com/lujun9972
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/freedos.png?itok=aOBLy7Ky (4 different color terminal windows with code)
[2]: https://opensource.com/article/19/8/what-are-environment-variables
[3]: https://opensource.com/article/19/7/master-ls-command