aboutsummaryrefslogtreecommitdiffstats
path: root/README.multi-tty
diff options
context:
space:
mode:
authorKaroly Lorentey2005-11-07 14:17:18 +0000
committerKaroly Lorentey2005-11-07 14:17:18 +0000
commit9684e4c92f12f7c31f5e6fda7742960b403395f6 (patch)
tree7dd95b31d3bfecc050a31d791c654e8d3b9669fc /README.multi-tty
parentcd0cf71c4f41023a8d9c20b3a26e44b980992b5a (diff)
downloademacs-9684e4c92f12f7c31f5e6fda7742960b403395f6.tar.gz
emacs-9684e4c92f12f7c31f5e6fda7742960b403395f6.zip
Update frames-on-display-list to accept terminal id numbers.
* lisp/frame.el (frames-on-display-list): Use terminal-id to get the display id. (terminal-id): Also accept X display strings and tty device names. git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-436
Diffstat (limited to 'README.multi-tty')
-rw-r--r--README.multi-tty39
1 files changed, 22 insertions, 17 deletions
diff --git a/README.multi-tty b/README.multi-tty
index 2bba1b9bcb5..ab43fc7c4e1 100644
--- a/README.multi-tty
+++ b/README.multi-tty
@@ -424,9 +424,6 @@ THINGS TO DO
424 instead of delete-frame-functions), 424 instead of delete-frame-functions),
425 after-delete-terminal-functions, after-create-terminal-functions. 425 after-delete-terminal-functions, after-create-terminal-functions.
426 426
427** If the first key pressed on a new tty terminal is a function key,
428 it is not recognized correctly. May be related to the bug below.
429
430** Fix set-input-mode for multi-tty. It's a truly horrible interface; 427** Fix set-input-mode for multi-tty. It's a truly horrible interface;
431 what if we'd blow it up into several separate functions (with a 428 what if we'd blow it up into several separate functions (with a
432 compatibility definition)? 429 compatibility definition)?
@@ -472,20 +469,6 @@ THINGS TO DO
472 frame-display terminal-of-frame 469 frame-display terminal-of-frame
473 delete-display delete-terminal 470 delete-display delete-terminal
474 471
475** The semantics of terminal-local variables are confusing; it is not
476 clear what binding is in effect in any given time. See if
477 current_kboard (or at least the terminal-local bindings exported to
478 Lisp) might be changed to be tied to the selected frame instead.
479 Currently, `function-key-map' and `key-translation-map' may be
480 accessed reliably only using the hackish
481 `(set-)terminal-local-value' functions.
482
483 Perhaps there should be a difference between `last-command' &co.
484 and these more conventional configuration variables.
485 (E.g. `symbol-value' would use current_kboard to access
486 `last-command', but SELECTED_FRAME()->display->kboard to get the
487 value of `function-key-map'.
488
489** The single-keyboard mode of MULTI_KBOARD is extremely confusing 472** The single-keyboard mode of MULTI_KBOARD is extremely confusing
490 sometimes; Emacs does not respond to stimuli from other keyboards. 473 sometimes; Emacs does not respond to stimuli from other keyboards.
491 At least a beep or a message would be important, if the single-mode 474 At least a beep or a message would be important, if the single-mode
@@ -1261,5 +1244,27 @@ DIARY OF CHANGES
1261 1244
1262 (Done in patch-431.) 1245 (Done in patch-431.)
1263 1246
1247-- The semantics of terminal-local variables are confusing; it is not
1248 clear what binding is in effect in any given time. See if
1249 current_kboard (or at least the terminal-local bindings exported to
1250 Lisp) might be changed to be tied to the selected frame instead.
1251 Currently, `function-key-map' and `key-translation-map' may be
1252 accessed reliably only using the hackish
1253 `(set-)terminal-local-value' functions.
1254
1255 Perhaps there should be a difference between `last-command' &co.
1256 and these more conventional configuration variables.
1257 (E.g. `symbol-value' would use current_kboard to access
1258 `last-command', but SELECTED_FRAME()->display->kboard to get the
1259 value of `function-key-map'.
1260
1261 (Fixed in patch-434.)
1262
1263-- If the first key pressed on a new tty terminal is a function key,
1264 it is not recognized correctly. May be related to the bug below.
1265
1266 (Seems to have been fixed as a side effect of patch-434. "The bug
1267 below" was the set-input-mode madness.)
1268
1264;;; arch-tag: 8da1619e-2e79-41a8-9ac9-a0485daad17d 1269;;; arch-tag: 8da1619e-2e79-41a8-9ac9-a0485daad17d
1265 1270