Differences between revisions 2 and 3
Revision 2 as of 2007-06-18 21:57:51
Size: 871
Editor: p54934E54
Comment:
Revision 3 as of 2008-02-19 20:54:35
Size: 1638
Editor: GreyCat
Comment: more (and improved) examples, link to a couple other FAQs
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
''Do not'' hard-code ANSI color escape sequences in your program! The {{{tput}}} command lets you interact with the terminal database in a sane way. ''Do not'' hard-code ANSI color escape sequences in your program! The {{{tput}}} command lets you interact with the terminal database in a sane way:
Line 8: Line 8:
  tput setaf 0; echo now we are back in black   tput bold; echo "boldface (and still green)"
  tput sgr0; echo back to normal
Line 13: Line 14:
If you don't know in advance what your user's terminal's default text color is, you can use {{{tput sgr0}}} to reset the colors to their default settings. This also removes boldface ({{{tput bold}}}), etc. {{{tput sgr0}}} resets the colors to their default settings. This also turns off boldface ({{{tput bold}}}), underline, etc.

If you want fancy colors in your prompt (in bash), consider using something manageable:

{{{
  RED=$(tput setaf 1)
  GREEN=$(tput setaf 2)
  BLUE=$(tput setaf 4)
  NORM=$(tput sgr0)
  PS1='\[$RED\]\u\[$NORM\]@\[$GREEN\]\h\[$NORM\]:\[$BLUE\]\w\[$NORM\]\$ '
}}}

Note that we do '''not''' hard-code ANSI color escape sequences. Instead, we [:BashFAQ#faq2:store the output] of the `tput` command into variables, which are then used when `$PS1` is expanded. Storing the values means we don't have to fork a `tput` process multiple times every time the prompt is displayed; `tput` is only invoked 4 times during [:DotFiles:shell startup]. The `\[` and `\]` symbols allow bash to understand which parts of the prompt cause no cursor movement; without them, [:BashFAQ#faq53:lines will wrap incorrectly].

Anchor(faq37)

How can I print text in various colors?

Do not hard-code ANSI color escape sequences in your program! The tput command lets you interact with the terminal database in a sane way:

  tput setaf 1; echo this is red
  tput setaf 2; echo this is green
  tput bold; echo "boldface (and still green)"
  tput sgr0; echo back to normal

tput reads the terminfo database which contains all the escape codes necessary for interacting with your terminal, as defined by the $TERM variable. For more details, see the terminfo(5) man page.

tput sgr0 resets the colors to their default settings. This also turns off boldface (tput bold), underline, etc.

If you want fancy colors in your prompt (in bash), consider using something manageable:

  RED=$(tput setaf 1)
  GREEN=$(tput setaf 2)
  BLUE=$(tput setaf 4)
  NORM=$(tput sgr0)
  PS1='\[$RED\]\u\[$NORM\]@\[$GREEN\]\h\[$NORM\]:\[$BLUE\]\w\[$NORM\]\$ '

Note that we do not hard-code ANSI color escape sequences. Instead, we [:BashFAQ#faq2:store the output] of the tput command into variables, which are then used when $PS1 is expanded. Storing the values means we don't have to fork a tput process multiple times every time the prompt is displayed; tput is only invoked 4 times during [:DotFiles:shell startup]. The \[ and \] symbols allow bash to understand which parts of the prompt cause no cursor movement; without them, [:BashFAQ#faq53:lines will wrap incorrectly].

See also [http://bash-hackers.org/wiki/doku.php?id=scripting:terminalcodes] for an overview.

BashFAQ/037 (last edited 2022-08-01 09:45:25 by 84)