aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGlenn Morris2009-06-16 02:55:46 +0000
committerGlenn Morris2009-06-16 02:55:46 +0000
commit6e270cdbc8608cd8cb28e1a11c0894678d89dd6f (patch)
tree03814dce48103c77468f667c4b10f766561f1c24
parentb59a8457e73346e43e91989870bc98e6a417b5c6 (diff)
downloademacs-6e270cdbc8608cd8cb28e1a11c0894678d89dd6f.tar.gz
emacs-6e270cdbc8608cd8cb28e1a11c0894678d89dd6f.zip
Merge in a few snippets just deleted from faq.texi.
-rw-r--r--etc/PROBLEMS9
1 files changed, 6 insertions, 3 deletions
diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index 8a14e1cdaf6..0654d00667f 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -1504,7 +1504,8 @@ There are three possible reasons why flow control could be taking place:
1504 1504
1505First of all, many terminals have a set-up mode which controls whether 1505First of all, many terminals have a set-up mode which controls whether
1506they generate XON/XOFF flow control characters. This must be set to 1506they generate XON/XOFF flow control characters. This must be set to
1507"no XON/XOFF" in order for Emacs to work. Sometimes there is an 1507"no XON/XOFF" in order for Emacs to work. (For example, on a VT220
1508you may select "No XOFF" in the setup menu.) Sometimes there is an
1508escape sequence that the computer can send to turn flow control off 1509escape sequence that the computer can send to turn flow control off
1509and on. If so, perhaps the termcap `ti' string should turn flow 1510and on. If so, perhaps the termcap `ti' string should turn flow
1510control off, and the `te' string should turn it on. 1511control off, and the `te' string should turn it on.
@@ -1631,12 +1632,14 @@ in termcap.c, tparam.c, term.c, scroll.c, cm.c or dispnew.c.
1631Some versions of rlogin (and possibly telnet) do not pass flow 1632Some versions of rlogin (and possibly telnet) do not pass flow
1632control characters to the remote system to which they connect. 1633control characters to the remote system to which they connect.
1633On such systems, emacs on the remote system cannot disable flow 1634On such systems, emacs on the remote system cannot disable flow
1634control on the local system. 1635control on the local system. Sometimes `rlogin -8' will avoid this
1636problem.
1635 1637
1636One way to cure this is to disable flow control on the local host 1638One way to cure this is to disable flow control on the local host
1637(the one running rlogin, not the one running rlogind) using the 1639(the one running rlogin, not the one running rlogind) using the
1638stty command, before starting the rlogin process. On many systems, 1640stty command, before starting the rlogin process. On many systems,
1639"stty start u stop u" will do this. 1641"stty start u stop u" will do this. On some systems, use
1642"stty -ixon" instead.
1640 1643
1641Some versions of tcsh will prevent even this from working. One way 1644Some versions of tcsh will prevent even this from working. One way
1642around this is to start another shell before starting rlogin, and 1645around this is to start another shell before starting rlogin, and