nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-01-10 01:48:00 +00:00
Code Issues Projects Releases Wiki Activity

Mention relationship between terminal types, keyboard sequences, and

Browse Source 
termcap/terminfo.  Suggested by Joachim Durchholz.

[originally from svn r6285]
This commit is contained in:
Ben Harris 2005-09-10 17:36:52 +00:00
parent c0d36aa00a
commit b65e905572
2 changed files with 19 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/config.but
View File

@ -416,7 +416,7 @@ other problems.
Note that this is \e{not} the feature of PuTTY which the server will Note that this is \e{not} the feature of PuTTY which the server will
typically use to determine your terminal type. That feature is the typically use to determine your terminal type. That feature is the
\q{Terminal-type string} in the Connection panel; see \q{\ii{Terminal-type} string} in the Connection panel; see
\k{config-termtype} for details. \k{config-termtype} for details.
You can include control characters in the answerback string using You can include control characters in the answerback string using
@ -502,7 +502,13 @@ state.
\H{config-keyboard} The Keyboard panel \H{config-keyboard} The Keyboard panel
The Keyboard configuration panel allows you to control the behaviour The Keyboard configuration panel allows you to control the behaviour
of the \i{keyboard} in PuTTY. of the \i{keyboard} in PuTTY. The correct state for many of these
settings depends on what the server to which PuTTY is connecting
expects. With a \i{Unix} server, this is likely to depend on the
\i\c{termcap} or \i\c{terminfo} entry it uses, which in turn is likely to
be controlled by the \q{\ii{Terminal-type} string} setting in the Connection
panel; see \k{config-termtype} for details. If none of the settings here
seems to help, you may find \k{faq-keyboard} to be useful.
\S{config-backspace} Changing the action of the \ii{Backspace key} \S{config-backspace} Changing the action of the \ii{Backspace key}
@ -1681,7 +1687,11 @@ connected to from lots of different types of terminal. In order to
send the right \i{control sequence}s to each one, the server will need send the right \i{control sequence}s to each one, the server will need
to know what type of terminal it is dealing with. Therefore, each of to know what type of terminal it is dealing with. Therefore, each of
the SSH, Telnet and Rlogin protocols allow a text string to be sent the SSH, Telnet and Rlogin protocols allow a text string to be sent
down the connection describing the terminal. down the connection describing the terminal. On a \i{Unix} server,
this selects an entry from the \i\c{termcap} or \i\c{terminfo} database
that tells applications what \i{control sequences} to send to the
terminal, and what character sequences to expect the \i{keyboard}
to generate.
PuTTY attempts to emulate the Unix \i\c{xterm} program, and by default PuTTY attempts to emulate the Unix \i\c{xterm} program, and by default
it reflects this by sending \c{xterm} as a terminal-type string. If it reflects this by sending \c{xterm} as a terminal-type string. If

12
doc/faq.but
View File

@ -779,8 +779,8 @@ your terminal runs the risk of sending the same control sequence by
accident, and cause unexpected changes in the window title. Don't do accident, and cause unexpected changes in the window title. Don't do
it. it.
\S{faq-password-fails}{Question} My keyboard stops working once \S{faq-password-fails}{Question} My \i{keyboard} stops working once
PuTTY displays the password prompt. PuTTY displays the \i{password prompt}.
No, it doesn't. PuTTY just doesn't display the password you type, so No, it doesn't. PuTTY just doesn't display the password you type, so
that someone looking at your screen can't see what it is. that someone looking at your screen can't see what it is.
@ -790,8 +790,8 @@ as a row of asterisks either. This is so that someone looking at
your screen can't even tell how \e{long} your password is, which your screen can't even tell how \e{long} your password is, which
might be valuable information. might be valuable information.
\S{faq-keyboard}{Question} One or more function keys don't do what I \S{faq-keyboard}{Question} One or more \I{keyboard}\i{function keys}
expected in a server-side application. don't do what I expected in a server-side application.
If you've already tried all the relevant options in the PuTTY If you've already tried all the relevant options in the PuTTY
Keyboard panel, you may need to mail the PuTTY maintainers and ask. Keyboard panel, you may need to mail the PuTTY maintainers and ask.
@ -812,8 +812,8 @@ application is expecting.
The simplest way to investigate this is to find some other terminal The simplest way to investigate this is to find some other terminal
environment, in which that function key \e{does} work; and then environment, in which that function key \e{does} work; and then
investigate what sequence the function key is sending in that investigate what sequence the function key is sending in that
situation. One reasonably easy way to do this on a Unix system is to situation. One reasonably easy way to do this on a \i{Unix} system is to
type the command \c{cat}, and then press the function key. This is type the command \i\c{cat}, and then press the function key. This is
likely to produce output of the form \c{^[[11~}. You can also do likely to produce output of the form \c{^[[11~}. You can also do
this in PuTTY, to find out what sequence the function key is this in PuTTY, to find out what sequence the function key is
producing in that. Then you can mail the PuTTY maintainers and tell producing in that. Then you can mail the PuTTY maintainers and tell