Mercurial > emacs
comparison etc/PROBLEMS @ 103445:a53a6689e178
Merge in a few snippets just deleted from faq.texi.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Tue, 16 Jun 2009 02:55:46 +0000 |
parents | ff7c2d7d29e6 |
children | c4fa6fe77406 |
comparison
equal
deleted
inserted
replaced
103444:61b1b668390e | 103445:a53a6689e178 |
---|---|
1502 2) Insufficient padding for the terminal in use | 1502 2) Insufficient padding for the terminal in use |
1503 3) Some sort of terminal concentrator or line switch is responsible | 1503 3) Some sort of terminal concentrator or line switch is responsible |
1504 | 1504 |
1505 First of all, many terminals have a set-up mode which controls whether | 1505 First of all, many terminals have a set-up mode which controls whether |
1506 they generate XON/XOFF flow control characters. This must be set to | 1506 they 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 |
1508 you may select "No XOFF" in the setup menu.) Sometimes there is an | |
1508 escape sequence that the computer can send to turn flow control off | 1509 escape sequence that the computer can send to turn flow control off |
1509 and on. If so, perhaps the termcap `ti' string should turn flow | 1510 and on. If so, perhaps the termcap `ti' string should turn flow |
1510 control off, and the `te' string should turn it on. | 1511 control off, and the `te' string should turn it on. |
1511 | 1512 |
1512 Once the terminal has been told "no flow control", you may find it | 1513 Once the terminal has been told "no flow control", you may find it |
1629 ** Control-S and Control-Q commands are ignored completely on a net connection. | 1630 ** Control-S and Control-Q commands are ignored completely on a net connection. |
1630 | 1631 |
1631 Some versions of rlogin (and possibly telnet) do not pass flow | 1632 Some versions of rlogin (and possibly telnet) do not pass flow |
1632 control characters to the remote system to which they connect. | 1633 control characters to the remote system to which they connect. |
1633 On such systems, emacs on the remote system cannot disable flow | 1634 On such systems, emacs on the remote system cannot disable flow |
1634 control on the local system. | 1635 control on the local system. Sometimes `rlogin -8' will avoid this |
1636 problem. | |
1635 | 1637 |
1636 One way to cure this is to disable flow control on the local host | 1638 One 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 |
1638 stty command, before starting the rlogin process. On many systems, | 1640 stty 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 |
1641 Some versions of tcsh will prevent even this from working. One way | 1644 Some versions of tcsh will prevent even this from working. One way |
1642 around this is to start another shell before starting rlogin, and | 1645 around this is to start another shell before starting rlogin, and |
1643 issue the stty command to disable flow control from that shell. | 1646 issue the stty command to disable flow control from that shell. |
1644 | 1647 |