mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-10 09:58:01 +00:00
Some blurb about terminal types and 256-colour xterms. Thanks to Dan
Nicolaescu for the suggestion. [originally from svn r4925]
This commit is contained in:
parent
27cad589cc
commit
f237e23aff
@ -1409,6 +1409,20 @@ This option is enabled by default. If it is disabled, PuTTY will
|
|||||||
ignore any control sequences sent by the server which use the
|
ignore any control sequences sent by the server which use the
|
||||||
extended 256-colour mode supported by recent versions of \cw{xterm}.
|
extended 256-colour mode supported by recent versions of \cw{xterm}.
|
||||||
|
|
||||||
|
If you have an application which is supposed to use 256-colour mode
|
||||||
|
and it isn't working, you may find you need to tell your server that
|
||||||
|
your terminal supports 256 colours. On Unix, you do this by ensuring
|
||||||
|
that the setting of \cw{TERM} describes a 256-colour-capable
|
||||||
|
terminal. You can check this using a command such as \c{infocmp}:
|
||||||
|
|
||||||
|
\c $ infocmp | grep colors
|
||||||
|
\c colors#256, cols#80, it#8, lines#24, pairs#256,
|
||||||
|
\e bbbbbbbbbb
|
||||||
|
|
||||||
|
If you do not see \cq{colors#256} in the output, you may need to
|
||||||
|
change your terminal setting. On modern Linux machines, you could
|
||||||
|
try \cq{xterm-256color}.
|
||||||
|
|
||||||
\S{config-boldcolour} \q{Bolded text is a different colour}
|
\S{config-boldcolour} \q{Bolded text is a different colour}
|
||||||
|
|
||||||
\cfg{winhelp-topic}{colours.bold}
|
\cfg{winhelp-topic}{colours.bold}
|
||||||
|
Loading…
Reference in New Issue
Block a user