diff options
author | Karoly Lorentey <[email protected]> | 2005-09-11 04:10:45 +0000 |
---|---|---|
committer | Karoly Lorentey <[email protected]> | 2005-09-11 04:10:45 +0000 |
commit | ee0bcfbce6e8f7055f483976a68b33a2bdd46d14 (patch) | |
tree | 1ed004198debdd902de8de2bfeac8c3891bf472c /README.multi-tty | |
parent | 62c5106ca59c5771ba2e62725985ba802afdc0d1 (diff) |
Set Emacs version number to 22.0.51 to allow parallel installations of CVS trunk and the multi-tty branch.
* README: Set Emacs version to 22.0.51.
* lispref/elisp.texi (EMACSVER): Set to 22.0.51.
* man/emacs.texi (EMACSVER): Set to 22.0.51.
* lisp/version.el (emacs-version): Set to 22.0.51.
git-archimport-id: [email protected]/emacs--multi-tty--0--patch-413
Diffstat (limited to 'README.multi-tty')
-rw-r--r-- | README.multi-tty | 44 |
1 files changed, 28 insertions, 16 deletions
diff --git a/README.multi-tty b/README.multi-tty index 39a1607cbd..9dc7f6b8bd 100644 --- a/README.multi-tty +++ b/README.multi-tty @@ -428,22 +428,6 @@ THINGS TO DO ** If the first key pressed on a new tty terminal is a function key, it is not recognized correctly. May be related to the bug below. -** Having {reset,init}_all_sys_modes in set-input-mode breaks arrow - keys on non-selected terminals under screen, and sometimes on other - terminal types as well. The other function keys continue to work - fine. Sometimes faces on these screens become garbled. - - This only seems to affect displays that are of the same terminfo - type as the selected one. Interestingly, in screen Emacs normally - reports the up arrow key as `M-o A', but after the above SNAFU, it - complains about `M-[ a'. UNIX ttys are a complete mystery to me, - but it seems the reset-reinitialize cycle somehow leaves the - non-selected terminals in a different state than usual. I have no - idea how this could happen. - - Currently set-input-mode resets only the currently selected - terminal, which seems to somehow work around the problem. - ** Fix set-input-mode for multi-tty. It's a truly horrible interface; what if we'd blow it up into several separate functions (with a compatibility definition)? @@ -1227,5 +1211,33 @@ DIARY OF CHANGES (Done, I hope.) +-- Having {reset,init}_all_sys_modes in set-input-mode breaks arrow + keys on non-selected terminals under screen, and sometimes on other + terminal types as well. The other function keys continue to work + fine. Sometimes faces on these screens become garbled. + + This only seems to affect displays that are of the same terminfo + type as the selected one. Interestingly, in screen Emacs normally + reports the up arrow key as `M-o A', but after the above SNAFU, it + complains about `M-[ a'. UNIX ttys are a complete mystery to me, + but it seems the reset-reinitialize cycle somehow leaves the + non-selected terminals in a different state than usual. I have no + idea how this could happen. + + Currently set-input-mode resets only the currently selected + terminal, which seems to somehow work around the problem. + + Update: + + Dan Nicolaescu <[email protected]> writes: + > Some terminals have 2 modes for cursor keys: Application Mode where + > the cursor keys transmit the codes defined in the terminfo entry, and + > Cursor mode. Applications have to send the smkx and rmkx terminfo + > strings to switch between the 2 modes. So Emacs (and emacsclient) have + > to send smkx when initializing and rmkx when quitting (or on + > suspend). + + (I think patch-370 fixed this.) + ;;; arch-tag: 8da1619e-2e79-41a8-9ac9-a0485daad17d |