Terminal (control-)codes are needed to give specific commands to your terminal. This can be related to switching colors or positioning the cursor, simply everything that can't be done by the application itself.
A terminal control code is a special sequence of characters that is printed (like any other text). If the terminal understands the code, it won't display the character-sequence, but will perform some action. You can always print the codes with a simple echo command - for the application, it's nothing special.
Note: I see that codes referenced as "Bash colors" sometimes (several "Bash tutorials" etc…): That's a retarded and completely incorrect definition.
Because there's a large number of different terminal control languages, usually a system has an intermediate-layer to talk to it. The real codes are looked up in a database for the currently detected terminal type and you give standardized requests to an API or (from the shell) to a command.
One of these commands is tput - it accepts a set of acronymes and parameters for them, looks up the correct codes for the detected terminal in the terminfo database and prints the correct codes (the terminal hopefully understands).
In this list I'll focus to ANSI/VT100 control codes for the most needed actions - take it as quick reference. The documentation of your terminal or the terminfo database is always the preferred source when something is unclear! Also the tput acronymes are the ones dedicated for ANSI escapes, usually!
Also I only listed the most relevant codes, of course, any ANSI or especially your nice terminal knows much more! But let's reduce to common shell scripting
Sometimes I didn't find a matching ANSI escape or vice versa - you'll see a
as code then - feel free to mail me or fix it!
The ANSI codes are always intoduced with an ESC character (ASCII 0x1B or octal 033) - this isn't part of the list, but you should avoid to use the ANSI codes directly - use the tput command!
All codes that can be used with tput can be found in terminfo(5). (on OpenBSD at least)
See OpenBSD's terminfo(5) under the Capabilities section. The cap-name is the code to use with tput, a description of each code is also provided.
The Ctrl-Key representation is simply associating the non-printable characters from ASCII code 1 with the printable (letter) characters from ASCII code 65 ("A"). ASCII code 1 would be ^A (Ctrl-A), while ASCII code 7 (BEL) would be ^G (Ctrl-G). This is a common representation (and input method) and historically comes from one of the VT series of terminals.
| Name | decimal | octal | hex | C-escape | Ctrl-Key | Description |
|---|---|---|---|---|---|---|
BEL | 7 | 007 | 0x07 | \a | ^G | Terminal bell |
BS | 8 | 010 | 0x08 | \b | ^H | Backspace |
HT | 9 | 011 | 0x09 | \t | ^I | Horizontal TAB |
LF | 10 | 012 | 0x0A | \n | ^J | Linefeed (newline) |
VT | 11 | 013 | 0x0B | \v | ^K | Vertical TAB |
FF | 12 | 014 | 0x0C | \f | ^L | Formfeed (also: New page NP) |
CR | 13 | 015 | 0x0D | \r | ^M | Carriage return |
ESC | 27 | 033 | 0x1B | <none> | ^[ | Escape character |
DEL | 127 | 177 | 0x7F | <none> | <none> | Delete character |
| ANSI | terminfo equivalent | Description |
|---|---|---|
[ <X> ; <Y> H[ <X> ; <Y> f | cup <X> <Y> | Home-positioning to X and Y coordinatestput takes 0-0 |
[ H | home | Home-positioning to root (0-0) |
7 | sc | Save current cursor position |
8 | rc | Restore current cursor position |
\b | cub1 | move left one space (backspace) |
VT100 [ ? 25 l | civis | switch cursor invisible |
VT100 [ ? 25 h | cvvis | switch cursor visible |
| ANSI | terminfo equivalent | Description |
|---|---|---|
[ K[ 0 K | el | Clear line from current cursor position to end of line |
[ 1 K | el1 | Clear line from beginning to current cursor position |
[ 2 K | el2 | Clear whole line (cursor position unchanged) |
| ANSI | terminfo equivalent | Description |
|---|---|---|
[ 0 m | sgr0 | Reset all attributes |
[ 1 m | bold | Set "bright" attribute |
[ 2 m | dim | Set "dim" attribute |
[ 4 m | set smul unset rmul | Set "underscore" (underlined text) attribute |
[ 5 m | blink | Set "blink" attribute |
[ 7 m | rev | Set "reverse" attribute |
[ 8 m | invis | Set "hidden" attribute |
| ANSI | terminfo equivalent | Description |
|---|---|---|
[ 3 0 m | setaf 0 | Set foreground to color #0 - black |
[ 3 1 m | setaf 1 | Set foreground to color #1 - red |
[ 3 2 m | setaf 2 | Set foreground to color #2 - green |
[ 3 3 m | setaf 3 | Set foreground to color #3 - yellow |
[ 3 4 m | setaf 4 | Set foreground to color #4 - blue |
[ 3 5 m | setaf 5 | Set foreground to color #5 - magenta |
[ 3 6 m | setaf 6 | Set foreground to color #6 - cyan |
[ 3 7 m | setaf 7 | Set foreground to color #7 - white |
[ 3 9 m | setaf 9 | Set default color as foreground color |
| ANSI | terminfo equivalent | Description |
|---|---|---|
[ 4 0 m | setab 0 | Set background to color #0 - black |
[ 4 1 m | setab 1 | Set background to color #1 - red |
[ 4 2 m | setab 2 | Set background to color #2 - green |
[ 4 3 m | setab 3 | Set background to color #3 - yellow |
[ 4 4 m | setab 4 | Set background to color #4 - blue |
[ 4 5 m | setab 5 | Set background to color #5 - magenta |
[ 4 6 m | setab 6 | Set background to color #6 - cyan |
[ 4 7 m | setab 7 | Set background to color #7 - white |
[ 4 9 m | setaf 9 | Set default color as background color |
Used capabilities: smcup, rmcup
For sure, you've already seen those programs that restore the terminal contents after they did their work (like vim). This can be done by the following codes:
# save, clear screen tput smcup clear # example "application" follows... read -n1 -p "Press any key to continue..." # example "application" ends here # restore tput rmcup
Thanks to greycat for finding this and sharing it!
Some terminal emulators support many additional colors. The most common extension used by xterm-compatible terminals supports 256 colors. These can be generated by tput with seta{f,b} [0-255] when the TERM value has a -256color suffix. Konsole supports full 24-bit colors, and as of KDE 4.9 any X11 color code can be written directly into a special escape sequence. Other terminals may offer similar extensions. Few, if any programs are able to make use of anything beyond 256, and tput doesn't know about them. Colors beyond 16 usually only apply to modern terminal emulators running in graphical environments.
The VT implemented in the Linux kernel supports only 16 colors, and the usual default terminfo entry for TERM=linux defines only 8. There is sometimes an alternate "linux-16color" that you can switch to to get the other 8 colors.
printf '%b\n' 'It is \033[31mnot\033[39m intelligent to use \033[32mhardcoded ANSI\033[39m codes!'
Directly inside the echo:
echo "TPUT is a $(tput setaf 2)nice$(tput setaf 9) and $(tput setaf 5)user friendly$(tput setaf 9) terminal capability database."
With preset variables:
COL_NORM="$(tput setaf 9)"
COL_RED="$(tput setaf 1)"
COL_GREEN="$(tput setaf 2)"
echo "It's ${COL_RED}red${COL_NORM} and ${COL_GREEN}green${COL_NORM} - have you seen?"
HOME function
home() {
# yes, actually not much shorter ;-)
tput home
}
#!/bin/bash
DATA[0]=" _/ _/ _/ _/ "
DATA[1]=" _/_/_/_/_/ _/_/_/ _/_/_/ _/_/_/ _/_/_/ "
DATA[2]=" _/ _/ _/ _/ _/ _/ _/_/ _/ _/"
DATA[3]="_/_/_/_/_/ _/ _/ _/ _/ _/_/ _/ _/ "
DATA[4]=" _/ _/ _/_/_/ _/_/_/ _/_/_/ _/ _/ "
# virtual coordinate system is X*Y ${#DATA} * 5
REAL_OFFSET_X=0
REAL_OFFSET_Y=0
draw_char() {
V_COORD_X=$1
V_COORD_Y=$2
tput cup $((REAL_OFFSET_Y + V_COORD_Y)) $((REAL_OFFSET_X + V_COORD_X))
printf %c ${DATA[V_COORD_Y]:V_COORD_X:1}
}
trap 'exit 1' INT TERM
trap 'tput setaf 9; tput cvvis; clear' EXIT
tput civis
clear
while :; do
for ((c=1; c <= 7; c++)); do
tput setaf $c
for ((x=0; x<${#DATA[0]}; x++)); do
for ((y=0; y<=4; y++)); do
draw_char $x $y
done
done
done
done
This is a slightly modified version of Charles Cooke's colorful Mandelbrot plot scripts ( original w/ screenshot) – ungolfed, optimized a bit, and without hard-coded terminal escapes. The colorBox function is memoized to collect tput output only when required and output a new escape only when a color change is needed. This limits the number of tput calls to at most 16, and reduces raw output by more than half. The doBash function uses integer arithmetic, but is still ksh93-compatible (run as e.g. bash ./mandelbrot to use it). The ksh93-only floating-point doKsh is almost 10x faster than doBash (thus the ksh shebang by default), but uses only features that don't make the Bash parser puke.
#!/usr/bin/env ksh
# Charles Cooke's 16-color Mandelbrot
# http://earth.gkhs.net/ccooke/shell.html
# Combined Bash/ksh93 flavors by Dan Douglas (ormaaj)
function doBash {
typeset P Q X Y a b c i v x y
for ((P=10**8,Q=P/100,X=320*Q/cols,Y=210*Q/lines,y=-105*Q,v=-220*Q,x=v;y<105*Q;x=v,y+=Y)); do
for ((;x<P;a=b=i=c=0,x+=X)); do
for ((;a**2+b**2<4*P**2&&i++<99;a=((c=a)**2-b**2)/P+x,b=2*c*b/P+y)); do :
done
colorBox $((i<99?i%16:0))
done
echo
done
}
function doKsh {
integer i
float a b c x=2.2 y=-1.05 X=3.2/cols Y=2.1/lines
while
for ((a=b=i=0;(c=a)**2+b**2<=2&&i++<99&&(a=a**2-b**2+x,b=2*c*b+y);)); do :
done
. colorBox $((i<99?i%16:0))
if ((x<1?!(x+=X):(y+=Y,x=-2.2))); then
print
((y<1.05))
fi
do :
done
}
function colorBox {
(($1==lastclr)) || printf %s "${colrs[lastclr=$1]:=$(tput setaf "$1")}"
printf '\u2588'
}
unset -v lastclr
((cols=$(tput cols)-1, lines=$(tput lines)))
typeset -a colrs
trap 'tput sgr0; echo' EXIT
${KSH_VERSION+. doKsh} ${BASH_VERSION+doBash}
A much more sophisticated version by Roland Mainz can be found here
Discussion
RE: your "Note: I found no code to entirely erase the current line ("delete line" is something else!). It might be a combination of positioning the cursor and erase to the end of line."
Try this: [ 2 K el2 Clear whole line
In the table showing
[ 3 9 m setaf 9 Set default foreground color
the Description "Set default foreground color" is ambiguous.
That phrase could mean either that the commands will 1) store the value of a specified color as the "default" color value, or that 2) a stored "default" color value will be used to re-set the current foreground or background color to a new value. Which is it? In one case there can be a visible change on the screen. In the other case, the will never be a visible change on the screen.
As it is, some people will create termcap files which gratuitously reset the display to the "default" colors, which makes using custom foreground and background colors impossible. Of course, this is just mean, and requires rewriting the termcap file.
Also, the Descriptions of the "Dim", "Bright", and "Reverse" attributes could actually say what these are suppose to do. For instance, what is suppose to happen when setting both "Dim" and "Bright"? Or, does "Reverse" apply to both the foreground and background colors? Does "Reverse" mean to exchange the foreground and background colors? Or to set some kind of "complement" color to each of the foreground and background?
These "Descriptions" that do not describe are not useful.
James
# print shortcuts for all ansi codes, NB: please add plus plus in for statements!
ansi-test() { for a in 0 1 4 5 7; do echo "a=$a " for (( f=0; f<=9; f++ )) ; do for (( b=0; b<=9; b++ )) ; do #echo -ne "f=$f b=$b" echo -ne "\\033[${a};3${f};4${b}m" echo -ne "\\\\\\\\033[${a};3${f};4${b}m" echo -ne "\\033[0m " done echo done echo done echo }Hi,
Very cool tutorial. I recently purchased a beagleboard XM, so this site is a perfect place to start serial port programming.
And the "silly but nice effects" is awesome. I love it!
Here's a link to a "cool splash screen for my website". Its just a Java animation... (open with Java web start - jws)
file:///home/aubrey/Downloads/circlescroller.jnlp
Best Regards.
Hi,
thank you
I don't think this link will work for anybody except you (file:)
This describes things from the display end. What about the keyboard? How does someone read the codes from the keyboard and figure out that the user pressed the up arrow key, for example?
I'm interested in this for using the bash read -s -n 1 mechanism to bring in keystrokes 1 character at a time and then try to figure out what key the user pressed. Up arrow for example is \E[A . I want to get the entire list of possible character combinations that are legitimate for a given environment.
The infocmp utility can dump the terminfo for a particular entity (xterm, linux, etc) but I can't find the equivalent for a keybaord.
A very good question. Sorry, I can't answer it. I think there are no such things as "standardized" key codes.