Mention relationship between terminal types, keyboard sequences, and

termcap/terminfo.  Suggested by Joachim Durchholz.

git-svn-id: svn://svn.tartarus.org/sgt/putty@6285 cda61777-01e9-0310-a592-d414129be87e

diff --git a/doc/config.but b/doc/config.but
index 2647189..6832229 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -416,7 +416,7 @@ other problems.
 
 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
 
 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

-\q{Terminal-type string} in the Connection panel; see
+\q{\ii{Terminal-type} string} in the Connection panel; see

 \k{config-termtype} for details.
 
 You can include control characters in the answerback string using
 \k{config-termtype} for details.
 
 You can include control characters in the answerback string using


@@ -502,7 +502,13 @@ state.
 \H{config-keyboard} The Keyboard panel
 
 The Keyboard configuration panel allows you to control the behaviour
 \H{config-keyboard} The Keyboard panel
 
 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
 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
 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
 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
 it reflects this by sending \c{xterm} as a terminal-type string. If
 
 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

diff --git a/doc/faq.but b/doc/faq.but
index 18d4290..abb4490 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -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
 it.
 
 accident, and cause unexpected changes in the window title. Don't do
 it.
 

-\S{faq-password-fails}{Question} My keyboard stops working once
-PuTTY displays the password prompt.
+\S{faq-password-fails}{Question} My \i{keyboard} stops working once
+PuTTY displays the \i{password prompt}.

 
 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.
 
 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.


@@ -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
 might be valuable information.
 
 your screen can't even tell how \e{long} your password is, which
 might be valuable information.
 

-\S{faq-keyboard}{Question} One or more function keys don't do what I
-expected in a server-side application.
+\S{faq-keyboard}{Question} One or more \I{keyboard}\i{function keys}
+don't do what I expected in a server-side application.

 
 If you've already tried all the relevant options in the PuTTY
 Keyboard panel, you may need to mail the PuTTY maintainers and ask.
 
 If you've already tried all the relevant options in the PuTTY
 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
 environment, in which that function key \e{does} work; and then
 investigate what sequence the function key is sending in that
 The simplest way to investigate this is to find some other terminal
 environment, in which that function key \e{does} work; and then
 investigate what sequence the function key is sending in that

-situation. One reasonably easy way to do this on a Unix system is to
-type the command \c{cat}, and then press the function key. This is
+situation. One reasonably easy way to do this on a \i{Unix} system is to
+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
 this in PuTTY, to find out what sequence the function key is
 producing in that. Then you can mail the PuTTY maintainers and tell
 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
 producing in that. Then you can mail the PuTTY maintainers and tell