# HG changeset patch
# User Glenn Morris <rgm@gnu.org>
# Date 1245120946 0
# Node ID a53a6689e17892f17424242a89522f9d69230ca6
# Parent  61b1b668390e35328c6b1584b6a7b46066272648
Merge in a few snippets just deleted from faq.texi.

diff -r 61b1b668390e -r a53a6689e178 etc/PROBLEMS
--- a/etc/PROBLEMS	Tue Jun 16 02:51:00 2009 +0000
+++ b/etc/PROBLEMS	Tue Jun 16 02:55:46 2009 +0000
@@ -1504,7 +1504,8 @@
 
 First of all, many terminals have a set-up mode which controls whether
 they generate XON/XOFF flow control characters.  This must be set to
-"no XON/XOFF" in order for Emacs to work.  Sometimes there is an
+"no XON/XOFF" in order for Emacs to work.  (For example, on a VT220
+you may select "No XOFF" in the setup menu.)  Sometimes there is an
 escape sequence that the computer can send to turn flow control off
 and on.  If so, perhaps the termcap `ti' string should turn flow
 control off, and the `te' string should turn it on.
@@ -1631,12 +1632,14 @@
 Some versions of rlogin (and possibly telnet) do not pass flow
 control characters to the remote system to which they connect.
 On such systems, emacs on the remote system cannot disable flow
-control on the local system.
+control on the local system.  Sometimes `rlogin -8' will avoid this
+problem.
 
 One way to cure this is to disable flow control on the local host
 (the one running rlogin, not the one running rlogind) using the
 stty command, before starting the rlogin process.  On many systems,
-"stty start u stop u" will do this.
+"stty start u stop u" will do this.  On some systems, use
+"stty -ixon" instead. 
 
 Some versions of tcsh will prevent even this from working.  One way
 around this is to start another shell before starting rlogin, and