README.multi-tty 55.4 KB
Newer Older
			-*- coding: utf-8; mode: text; -*-
2 3 4

5 6
This branch implements support for opening multiple, different tty
devices and simultaneous X and tty frames from a single Emacs session.

8 9 10 11
Some use cases:
Emacs is notoriously slow at startup, so most people use another
editor or emacsclient for quick editing jobs from the console.
Unfortunately, emacsclient was very awkward to use, because it did not
support opening a new Emacs frame on the current virtual tty.
13 14 15 16 17 18 19 20 21
Now, with multi-tty support, it can do that.  (Emacsclient starts up
faster than vi!)

Some Gnus users (including me) run Gnus in an X frame in its own Emacs
instance, which they typically leave running for weeks.  It would be
nice if they could connect to this instance from a remote ssh session
and check their messages without opening a remote X frame or resorting
to gnus-slave.

22 23

25 26 27 28
The following is a (sadly incomplete) list of people who have
contributed to the project by testing, submitting patches, bug
reports, and suggestions.  Thanks!

Bernard Adrian <>
30 31 32
ARISAWA Akihiro <>
Vincent Bernat <>
Han Boetes <>
Francisco Borges <>
Damien Cassou <>
35 36 37
Robert J. Chassell <>
Romain Francoise <>
Ami Fischman <>
Noah Friedman <>
Friedrich Delgado Friedrichs <>
40 41
Samium Gromoff <>
Mikhail Gusarov <>
Eric Hanchrow <>
43 44 45 46 47
IRIE Tetsuya <>
Yoshiaki Kasahara <>
Bas Kok <>
Jurej Kubelka <>
David Lichteblau <>
Richard Lewis <>
mace <>
Suresh Madhu <>
51 52 53 54 55 56 57 58
Xavier Mallard <>
Istvan Marko <>
Ted Morse <>
Gergely Nagy <>
Dan Nicolaescu <>
Kalle Olavi Niemitalo <>
Mark Plaksin <>
Frank Ruell <>
Tom Schutzer-Weissmann <>
Joakim Verona <>
Dan Waber <>
62 63 64 65 66 67
and many others.

Richard Stallman was kind enough to review an earlier version of my

68 69 70 71 72 73 74 75

The branch is now very stable and almost full-featured.  All of the
major problems have been fixed, only a few minor issues remain.  (It
still needs to be ported to Windows/Mac/DOS, though.)  Both multiple
tty device support and simultaneous X and tty frame support works
fine.  Emacsclient has been extended to support opening new tty and X
frames.  It has been changed to open new Emacs frames by default.
77 78

The multi-tty branch has been scheduled for inclusion in the next
Karoly Lorentey's avatar
Karoly Lorentey committed
major release of Emacs (version 23).  I expect the merge into the
development trunk to occur sometime during next year (2006), after the
81 82
merge of the Unicode branch.

Karoly Lorentey's avatar
Karoly Lorentey committed
83 84 85
Tested on GNU/Linux, Solaris 8, FreeBSD and OpenBSD.  Please let me
know if you succeed or fail to use it on other platforms---I'll have a
few tricky test cases for you.
86 87 88

Known problems:

Karoly Lorentey's avatar
Karoly Lorentey committed
        * GTK support.  If you compile your Emacs with the GTK
90 91 92 93 94 95 96 97
          toolkit, some functionality of multi-tty may be lost.  In
          particular, you may get crashes while working on multiple X
          displays at once.  Previous releases of GTK had limitations
          and bugs that prevented full-blown multi-display support in
          Emacs.  (GTK crashed when Emacs tries to disconnect from an
          X server.)  Things are much improved in the current GTK
          version, but if you do experience crashes in libgtk, try
          compiling Emacs with the Lucid toolkit instead.
Karoly Lorentey's avatar
Karoly Lorentey committed

99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
        * The single-kboard mode.

	  If your multi-tty Emacs session seems to be frozen, you
	  probably have a recursive editing session or a pending
	  minibuffer prompt (which is a kind of recursive editing) on
	  another display.  To unfreeze your session, switch to that
	  display and complete the recursive edit, for example by
	  pressing C-] (`abort-recursive-edit').

	  I am sorry to say that currently there is no way to break
	  out of this "single-kboard mode" from a frozen display.  If
	  you are unable to switch to the display that locks the
	  others (for example because it is on a remote computer),
	  then you can use emacsclient to break out of all recursive
	  editing sessions:

		emacsclient -e '(top-level)'

	  Note that this (perhaps) unintuitive behaviour is by design.
	  Single-kboard mode is required because of an intrinsic Emacs
	  limitation that is very hard to eliminate.  (This limitation
	  is related to the single-threaded nature of Emacs.)

	  I plan to implement better user notification and support for
	  breaking out of single-kboard mode from locked displays.

Jason Rumney's avatar
Jason Rumney committed
	* Mac and DOS support is broken, doesn't even
126 127 128 129 130 131
  	  compile.  Multiple display support will probably not provide
  	  new Emacs features on these systems, but the multi-tty
  	  branch changed a few low-level interfaces, and the
  	  system-dependent source files need to be adapted
  	  accordingly.  The changes are mostly trivial, so almost
  	  anyone can help, if only by compiling the branch and
  	  reporting the compiler errors.

134 135 136 137


To get the branch, check out the "multi-tty" CVS branch from Emacs CVS.
Karoly Lorentey's avatar
Karoly Lorentey committed

Alternatively, you can use Bazaar version 1 (not 2) or tla:
Karoly Lorentey's avatar
Karoly Lorentey committed

142 143
	baz register-archive
	baz get <directory>
Karoly Lorentey's avatar
Karoly Lorentey committed


Karoly Lorentey's avatar
Karoly Lorentey committed
146 147

The multi-tty branch is compiled the same way as Emacs itself:

Karoly Lorentey's avatar
Karoly Lorentey committed
151 152
	make maintainer-clean  # (If you have compiled Emacs before)

	./configure <your favourite options>
	make bootstrap
155 156
	make install

Karoly Lorentey's avatar
Karoly Lorentey committed
157 158 159 160 161
If you have strange compilation errors, they may be caused by old
*.elc files that are left over from an earlier bootstrap.  The `make
maintainer-clean' target deletes them, so it is a good idea to run
that before reporting a bug.  (Emacs requires a clean recompilation
after certain kinds of source code changes.)

Karoly Lorentey's avatar
Karoly Lorentey committed
163 164 165 166

To test the multi-tty branch, start up the Emacs server with the
167 168 169
following commands:

	M-x server-start

172 173
and then (from a shell prompt on another terminal) start emacsclient
174 175
	emacsclient -t /optional/file/names...   (for a tty frame)
	emacsclient /optional/file/names...      (for an X frame)

(Make sure both emacs and emacsclient are multi-tty versions.)
Karoly Lorentey's avatar
Karoly Lorentey committed
You'll hopefully have two fully working, independent frames on
separate terminals. The new frame is closed automatically when you
Karoly Lorentey's avatar
Karoly Lorentey committed
180 181 182
finish editing the specified files (C-x #), but delete-frame (C-x 5 0)
also works.  Of course, you can create frames on more than two tty

Creating new frames on the same tty with C-x 5 2 (make-frame-command)
185 186
works, and behaves the same way as in previous Emacs versions.  If you
exit emacs, all terminals should be restored to their previous states.

188 189
This is work in progress, and probably full of bugs.  It is a good
idea to run emacs from gdb, so that you'll have a live instance to
190 191 192
debug if something goes wrong.  Please send your bug reports to  Please don't forget to mention that you are
using the multi-tty branch.
Karoly Lorentey's avatar
Karoly Lorentey committed

194 195 196

197 198
I think the best way to use the new Emacs is to have it running inside
a disconnected GNU screen session, and always use emacsclient for
199 200 201 202 203 204 205
normal work.  One advantage of this is that not a single keystroke of
your work will be lost if the display device that you are using
crashes, or the network connection times out, or whatever.  (I had an
extremely unstable X server for some time while I was developing these
patches, and running Emacs this way has saved me a number of M-x
recover-session invocations.)

206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271
I use the following two bash scripts to handle my Emacs sessions:

# Usage: connect-emacs <name> <args>...
# Connects to the Emacs instance called NAME.  Starts up the instance
# if it is not already running.  The rest of the arguments are passed
# to emacsclient.

if [ -z "$name" ]; then
    echo "Usage: connect_emacs <name> <args>..." >&2
    exit 1
preload-emacs "$name" wait
/usr/bin/emacsclient.emacs-multi-tty -s "$name" "$@"

# Usage: preload-emacs <name> [<waitp>]
# Preloads the Emacs instance called NAME in a detached screen
# session.  Does nothing if the instance is already running.  If WAITP
# is non-empty, the function waits until the server starts up and
# creates its socket; otherwise it returns immediately.

emacs=/usr/bin/emacs-multi-tty # Or wherever you installed your multi-tty Emacs

if [ -z "$name" ]; then 
    echo "Usage: preload_emacs <name> [<waitp>]" >&2
    exit 1

if [ ! -e "$screendir"/*."$name" ]; then
    if [ -e "$serverdir/$name" ]; then
	# Delete leftover socket (for the wait option)
	rm "$serverdir/$name"
    screen -dmS "$name" "$emacs" -nw --eval "(setq server-name \"$name\")" -f server-start
if [ ! -z "$waitp" ]; then
    while [ ! -e "$serverdir/$name" ]; do sleep 0.1; done

I have the following in my profile to have two instances automatically
preloaded for editing and email:

	preload-emacs editor
	preload-emacs gnus

It is useful to set up short aliases for connect-emacs.  I use the

	alias edit="connect-emacs editor"
	alias e=edit
	alias et="connect-emacs editor -t"
	alias gnus="connect-emacs gnus"


274 275 276

See the ChangeLog.multi-tty files in the source tree.

279 280 281

For the NEWS file:  (Needs much, much work)

284 285 286 287 288 289 290 291
** Support for multiple terminal devices and simultaneous graphical
   and tty frames has been added.  You can test for the presence of
   this feature in your Lisp code by testing for the `multi-tty'

*** The `window-system' variable has been made frame-local. The new
    `initial-window-system' variable contains the `window-system'
    value for the first frame.

293 294
*** You can specify a terminal device (`tty' parameter) and a terminal
    type (`tty-type' parameter) to `make-terminal-frame'.

296 297 298 299 300
*** The new function `make-frame-on-tty' allows you to create a new
    frame on another tty device interactively.

*** The function `make-frame-on-display' now works during a tty
    session, and `make-frame-on-tty' works during a graphical session.

*** Emacsclient has been extended to support opening a new terminal
Karoly Lorentey's avatar
Karoly Lorentey committed
303 304 305
    frame. Its behaviour has been changed to open a new Emacs frame by
    default.  Use the -c option to get the old behavior of opening
    files in the currently selected Emacs frame.

307 308
*** C-z now invokes `suspend-frame', C-x C-c now invokes

*** New functions: frame-tty-name, frame-tty-type, delete-tty,
311 312 313
    suspend-tty, resume-tty, terminal-id, terminal-parameters,
    terminal-parameter, set-terminal-parameter,
    modify-terminal-parameters, environment, let-environment

*** New variables: local-key-translation-map, local-function-key-map

317 318
*** The `keyboard-translate-table' variable and the terminal and
    keyboard coding systems have been made terminal-local.

320 321 322 323 324
*** In addition to the global key-translation-map and
    function-key-map, Emacs has terminal-local
    local-key-translation-map and local-function-key-map variables,
    and uses them instead of the global keymaps to set up translations
    and function key sequences relevant to a specific terminal device.

*** talk.el has been extended for multiple tty support.

Karoly Lorentey's avatar
Karoly Lorentey committed
328 329 330 331 332
* * *

(The rest of this file consists of my development notes and as such it
is probably not very interesting for anyone else.)

333 334

** See if `tty-defined-color-alist' needs to be terminal-local.
337 338 339 340 341
   Update: Dan says it should be, so convert it.

** Mikhail Gusarov suggest to add a hook akin to
   `after-make-frame-functions' that is called whenever Emacs connects
   to a new terminal.  Good idea!

Karoly Lorentey's avatar
Karoly Lorentey committed
343 344
** emacsclient -t on the console does not work after su.  You have to
   use non-root accounts or start as root to see this.

Karoly Lorentey's avatar
Karoly Lorentey committed
346 347
   	Login: root
	# su lorentey
349 350 351 352 353 354 355 356
	$ emacsclient -t
	*ERROR*: Could not open file: /dev/tty1

   The tty can be opened as /dev/tty by emacsclient, but not by Emacs.
   This seems to be a serious problem.  Currently my only idea is to
   bring back the ugly pty proxy hack from the initial versions of
   multi-tty.  Suggestions would be appreciated.

Karoly Lorentey's avatar
Karoly Lorentey committed
357 358 359 360 361 362
   Update: we could change emacsclient to pass its open file
   descriptor to the Emacs process.  Unfortunately, this requires a
   new Lisp-level Emacs API, and as file descriptors are not otherwise
   exported to Lisp, this approach seems at least as ugly as the pty
   proxy idea.

363 364 365
** lisp/vc.el depends on the terminal type during load time.
   `vc-annotate-color-map' is one example that needs to be fixed.

366 367 368 369 370 371
** Understand how `quit_throw_to_read_char' works, and fix any bugs
   that come to light.

** See if getcjmp can be eliminated somehow.  Why does Emacs allow
   asynchronous input processing while it's reading input anyway?

372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396
** `delete-frame' events are handled by `special-event-map'
   immediately when read by `read_char'.  This is fine but it prevents
   higher-level keymaps from binding that event to get notified of the
   deleted frame.

   Sometimes it would be useful for Lisp code to be notified of frame
   deletions after they have happened, usually because they want to
   clean up after the deleted frame.  Not all frame-local states can
   be stored as a frame parameter.  For example,
   `display-splash-screen' uses `recursive-edit' with a special keymap
   override to create its buffer---and it leads to all kinds of
   nastiness if Emacs stays in this recursive edit mode after the
   frame containing the splash screen is deleted.  Basically, the
   splash-screen implementation wants to throw out of the recursive
   edit when the frame is deleted; however, it is not legal to throw
   from `delete-frame-functions' because `delete-frame' must not fail.
   (Introducing `delete-frame-after-functions' would not help either
   because `delete-frame' may not fail at that time either.)

   Currently `fancy-splash-screens' installs a
   `delete-frame-functions' hook that sets up a timer to exit the
   recursive edit.  This is an adequate solution, but it would perhaps
   be better to have something like a `frame-deleted' event that could
   be bound in the normal way.

397 398 399 400
** Trouble: `setenv' doesn't actually set environment variables in the
   Emacs process.  This defeats the purpose of the elaborate
   `server-with-environment' magic around the `tgetent' call in
   `init_tty'.  D'oh.
401 402 403 404 405 406 407

** (Possibly) create hooks in struct device for creating frames on a
   specific terminal, and eliminate the hackish terminal-related frame
   parameters (display, tty, tty-type).

408 409 410 411

** Decide whether to keep the C implementation of terminal parameters,
   or revert to the previous, purely Lisp code.  It turned out that
   local environments do not need terminal parameters after all.
412 413 414 415 416

** Move Fsend_string_to_terminal to term.c, and declare get_named_tty
   as static, removing it from dispextern.h.
   Move fatal to emacs.c and declare it somewhere.

417 418 419 420
** Search for `suspend-emacs' references and replace them with
   `suspend-frame', if necessary.  Ditto for `save-buffers-kill-emacs'
   vs. `save-buffers-kill-display'.

421 422 423
** Emacs crashes when a tty frame is resized so that there is no space
   for all its windows.  (Tom Schutzer-Weissmann)

424 425
** Report GTK multi-display problems to GTK maintainers.  For extra
   credit, fix them.

427 428 429 430
   Currently you can not connect to new X displays when you compile
   Emacs with GTK support.  If you want to play around with GTK
   multidisplay (and don't mind core dumps), you can edit src/config.h
   and define HAVE_GTK_MULTIDISPLAY there by hand.
432 433

434 435 436
   Update: Han reports that GTK+ version 2.8.9 almost gets display
   disconnects right.  GTK will probably be fully fixed by the time
   multi-tty gets into the trunk.

438 439 440 441
   Update: I am still having problems with GTK+ 2.8.10.  I have the
   impression that the various multidisplay fixes will only get
   released in GTK+ 2.10.

Karoly Lorentey's avatar
Karoly Lorentey committed
442 443 444 445 446
** Audit `face-valid-attribute-values' usage in customize and
   elsewhere.  Its return value depends on the current window system.
   Replace static initializers using it with runtime functions.  For
   example, custom's buttons are broken on non-initial device types.

447 448 449
** Possibly turn off the double C-g feature when there is an X frame.
   C.f. (emacs)Emergency Escape.

** frames-on-display-list should also accept frames.

452 453 454 455
** Consider the `tty-type' frame parameter and the `display-tty-type'
   function.  They serve the exact same purpose.  I think it may be
   a good idea to eliminate one of them, preferably `tty-type'.

456 457 458 459
** The handling of lisp/term/*.el, and frame creation in general, is a
   big, big mess.  How come the terminal-specific file is loaded by
   tty-create-frame-with-faces?  I don't think it is necessary to load
   these files for each frame; once per terminal should be enough.
460 461
   Update: lisp/term/*.el is not loaded repeatedly anymore, but
   faces.el still needs to be cleaned up.
462 463 464 465

** Fix frame-set-background-mode in this branch.  It was recently
   changed in CVS, and frame.el in multi-tty has not yet been adapted
   for the changes.  (It needs to look at
   default-frame-background-mode.)  (Update: maybe it is fixed now;
467 468 469 470 471
   needs testing.) (Note that the byte compiler has this to say about

	term/rxvt.el:309:17:Warning: assignment to free variable
472 473 474 475

** I think `(set-)terminal-local-value' and the terminal parameter
   mechanism should be integrated into a single framework.

476 477 478 479 480
   (Update: `(set-)terminal-local-value' is now eliminated, but the
   terminal-local variables should still be accessible as terminal
   parameters.  This also applies to `display-name' and similar

481 482 483 484
** Add the following hooks: after-delete-frame-hook (for server.el,
   instead of delete-frame-functions),
   after-delete-terminal-functions, after-create-terminal-functions.

485 486
** BULK RENAME: The `display-' prefix of new Lisp-level functions
   conflicts with stuff like `display-time-mode'.  Use `device-'
487 488
   or `terminal-' instead.  I think I prefer `terminal-'.

Karoly Lorentey's avatar
Karoly Lorentey committed
489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515
   It turns out that most of the offending Lisp functions were defined
   in the trunk.  Therefore, compatibility aliases should be defined
   for the following names:

    display-color-cells			terminal-color-cells
    display-color-p			terminal-color-p
    display-graphic-p			terminal-graphic-p
    display-grayscale-p			terminal-grayscale-p
    display-images-p			terminal-images-p
    display-mm-height			terminal-mm-height
    display-mm-width			terminal-mm-width
    display-mouse-p			terminal-mouse-p
    display-multi-font-p		terminal-multi-font-p
    display-multi-frame-p		terminal-multi-frame-p
    display-pixel-height		terminal-pixel-height
    display-pixel-width			terminal-pixel-width
    display-pixels-per-inch		terminal-pixels-per-inch
    display-planes			terminal-planes
    display-popup-menus-p		terminal-popup-menus-p
    display-save-under			terminal-save-under
    display-screens			terminal-screens
    display-supports-face-attributes-p	terminal-supports-face-attributes-p
    display-visual-class		terminal-visual-class
    framep-on-display			framep-on-terminal
    frames-on-display-list		frames-on-terminal-list

   The following functions were introduced in the multi-tty branch, and
   were renamed without aliases:
Karoly Lorentey's avatar
Karoly Lorentey committed

518 519
    delete-display			delete-terminal
    display-controlling-tty-p           controlling-tty-p
Karoly Lorentey's avatar
Karoly Lorentey committed
520 521 522
    display-list                        terminal-list
    display-live-p                      terminal-live-p
    display-name                        terminal-name
523 524 525
    display-tty-type                    tty-type
    frame-display                       frame-terminal
    selected-display			selected-terminal
Karoly Lorentey's avatar
Karoly Lorentey committed

527 528 529 530 531 532 533 534 535
** The single-keyboard mode of MULTI_KBOARD is extremely confusing
   sometimes; Emacs does not respond to stimuli from other keyboards.
   At least a beep or a message would be important, if the single-mode
   is still required to prevent interference.  (Reported by Dan

   Update: selecting a region with the mouse enables single_kboard
   under X.  This is very confusing.

536 537 538 539
   Update: After discussions with Richard Stallman, this will be
   resolved by having locked displays warn the user to wait, and
   introducing a complex protocol to remotely bail out of
   single-kboard mode by pressing C-g.
540 541

   Update: Warning the user is not trivial to implement, as Emacs has
542 543 544 545 546 547 548
   only one echo area, shared by all frames.  Ideally the warning
   should not be displayed on the display that is locking the others.
   Perhaps the high probability of user confusion caused by
   single_kboard mode deserves a special case in the display code.
   Alternatively, it might be good enough to signal single_kboard mode
   by changing the modelines or some other frame-local display element
   on the locked out displays.

550 551
   Update: In fact struct kboard does have an echo_string slot.

552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578
** The session management module is prone to crashes when the X
   connection is closed and then later I try to connect to a new X

	#0  0xb7ebc806 in SmcGetIceConnection () from /usr/X11R6/lib/
	#1  0x080e6641 in x_session_check_input (bufp=0xbf86c9c0) at xsmfns.c:144
	#2  0x080d3bbc in XTread_socket (device=0xa722ff8, expected=1, hold_quit=0xbf86ca90) at xterm.c:7037
	#3  0x080fa404 in read_avail_input (expected=1) at keyboard.c:6696
	#4  0x080fa4ca in handle_async_input () at keyboard.c:6900
	#5  0x080d51fa in x_term_init (display_name=162628899, xrm_option=0x0, resource_name=0x857068c "emacs") at xterm.c:10622
	#6  0x080d920e in x_display_info_for_name (name=162628899) at xfns.c:3975
	#7  0x080d92f9 in check_x_display_info (object=1) at xfns.c:274
	#8  0x080d97b8 in Fx_create_frame (parms=151221485) at xfns.c:3016
	#9  0x0815bf72 in Ffuncall (nargs=2, args=0xbf86ceec) at eval.c:2851

   I installed a workaround to prevent this.  The X session manager is
   only contacted when the very first display in the Emacs session is
   an X display.  Also, x_delete_display() on this display aborts
   session management, and XTread_socket only calls
   x_session_check_input when it is called for the display that the
   session was opened on.  While this does not really fix the bug, it
   makes it much less frequent, because session manager support will
   not normally be enabled when Emacs can survive the shutdown of the
   X server.

   See if xsmfns.c should be updated.

579 580 581
** Hunt down display-related functions in frame.el and extend them all
   to accept display ids.

582 583 584
** rif->flush_display_optional (NULL) calls should be replaced by a
   new global function.

585 586
** The set-locale-environment hack (adding the DISPLAY option) should
   be replaced with a clean design.

588 589
** standard-display-table should be display-local.
   standard-display-european should be display-local.

591 592 593 594
** With iswitchb-default-method set to 'always-frame, only frames on
   the current display should be considered.  This might involve
   extending `get-buffer-window'.

595 596 597 598 599 600 601
** Have a look at Vlocale_coding_system.  Seems like it would be a
   tedious job to localize it, although most references use it for
   interfacing with libc and are therefore OK with the global

   Exceptions found so far: x-select-text and

Karoly Lorentey's avatar
Karoly Lorentey committed
603 604
** Have a look at fatal_error_hook.

Karoly Lorentey's avatar
Karoly Lorentey committed
605 606
** Have a look at set_frame_matrix_frame.

Karoly Lorentey's avatar
Karoly Lorentey committed
607 608
** Check if we got term-setup-hook right.

609 610 611 612
** I think tip_frame should be display-local.

** Check display reference count handling in x_create_tip_frame.

613 614 615 616 617 618 619 620
** make-frame does not correctly handle extra parameters in its

	(frame-parameter (make-frame (list (cons 'foobar 42))) 'foobar)
		=> nil

   (This is likely an error in the CVS trunk.)

Karoly Lorentey's avatar
Karoly Lorentey committed
621 622 623
** Dan Nicolaescu suggests that -nw should be added as an alias for -t
   in emacsclient.  Good idea.  (Alas, implementing this is not
   trivial, getopt_long does not seem to support two-letter ``short''
   options.  Patches are welcome.)
Karoly Lorentey's avatar
Karoly Lorentey committed
625 626 627 628

** Mark Plaksin suggests that emacsclient should accept the same
   X-related command-line arguments as Emacs.  Most of the X-related
   argument-handling is done in Lisp, so this should be quite easy to
629 630
   implement.  (For example, Samium Gromoff wants emacsclient to
   support --geometry; implementing this would add that support.)

Karoly Lorentey's avatar
Karoly Lorentey committed
632 633 634 635
** Gergely Nagy suggests that C-x # should only kill the current
   frame, not any other emacsclient frame that may have the same file
   opened for editing.  I think I agree with him.

636 637 638 639
** Very strange bug: visible-bell does not work on secondary
   terminals in xterm and konsole.  The screen does flicker a bit,
   but it's so quick it isn't noticable.

640 641 642
   (Update: This is probably some problem with padding or whatnot on
   the secondary terminals.)

** Move baud_rate to struct display.
644 645 646

** Implement support for starting an interactive Emacs session without
   an initial frame.  (The user would connect to it and open frames
Karoly Lorentey's avatar
Karoly Lorentey committed
   later, with emacsclient.)

649 650 651 652
** Fix Mac support (I can't do this entirely myself).  Note that the
   current state of Mac-specific source files in the multi-tty tree
   are not useful; before starting work on Mac support, revert to
   pristine, pre-multi-tty versions.

654 655 656 657
** Fix DOS support (I can't do this entirely myself).  Note that the
   current state of DOS-specific source files in the multi-tty tree
   are not useful; before starting work on DOS support, revert to
   pristine, pre-multi-tty versions.

Jason Rumney's avatar
Jason Rumney committed
659 660 661 662 663 664
** Fix Windows support. Currently bootstraping works on w32, but Emacs
   crashes on startup and none of the multi-tty features are
   implemented. Many XXX comments mark things that probably need
   updating, ChangeLogs will help in spotting changes to X specific
   files that may need porting.

665 666
** Do a grep on XXX and ?? for more issues.

667 668
** flow-ctrl.el must be updated.

669 670
** Fix stuff_char for multi-tty.  Doesn't seem to be of high priority.

671 672 673 674

(ex-TODO items with explanations.)

-- Introduce a new struct for terminal devices.

   (Done, see struct tty_output.  The list of members is not yet
679 680 681 682 683 684 685 686 687 688

-- Change the bootstrap procedure to initialize tty_list.

   (Done, but needs review.)

-- Change make-terminal-frame to support specifying another tty.

   (Done, new frame parameters: `tty' and `tty-type'.)

689 690 691
-- Implement support for reading from multiple terminals.

   (Done, read_avail_input tries to read from each terminal, until one
   succeeds.  MULTI_KBOARD is not used.  Secondary terminals don't send

695 696
   (Update: They do, now.)

697 698
   (Update2: After enabling X, they don't.)

-- other-frame should cycle through the frames on the `current'
   terminal only.

   (Done, by trivially modifiying next_frame and prev_frame.)
703 704

-- Support different terminal sizes.

706 707 708 709 710
   (Done, no problem.)

-- Make sure terminal resizes are handled gracefully.  (Could be

711 712
   (Done.  We don't get automatic SIGWINCH for additional ttys,
713 714 715

-- Extend emacsclient to automatically open a new tty when it connects
   to Emacs.

717 718
   (Done.  It's an ugly hack, needs more work.)

719 720
-- Redisplay must refresh the topmost frame on *all* terminals, not
   just the initial terminal.

   (Done, but introduced an ugly redisplay problems.  Ugh.)

724 725
-- Fix redisplay problems.

726 727
   (Done; it turned out that the entire Wcm structure must be moved
   inside tty_output.  Why didn't I catch this earlier?)
728 729 730 731 732 733 734 735 736 737

-- Provide a way for emacsclient to tell Emacs that the tty has been

   (Done, simply forward the SIGWINCH signal.)

-- Each keypress should automatically select the frame corresponding
   to the terminal that it was coming from.  This means that Emacs
   must know from which terminal the last keyboard event came from.

738 739
   (Done, it was quite simple, the input event system already
   supported multiple frames.)
740 741 742 743

-- Fix SIGIO issue with secondary terminals.

   (Done, emacsclient signals Emacs after writing to the proxy pseudo
744 745
   terminal.  Note that this means that multi-tty does not work with
   raw ttys!)

Karoly Lorentey's avatar
Karoly Lorentey committed
747 748 749
   (Update: This is bullshit.  There is a read_input_waiting function,
   extend that somehow.)

750 751 752 753
   (Update of update: The first update was not right either, extending
   read_input_waiting was not necessary.  Secondary ttys do seem to
   send signals on input.)

754 755
   (Update^3: Not any more.)

756 757 758 759 760 761 762 763 764 765
-- Make make-terminal-frame look up the `tty' and `tty-type' frame
   parameters from the currently selected terminal before the global


-- Put all cached terminal escape sequences into struct tty_output.
   Currently, they are still stored in global variables, so we don't
   really support multiple terminal types.

   (Done.  It was not fun.)
767 768

-- Implement sane error handling after initialization.  (Currently
769 770 771
   emacs exits if you specify a bad terminal type.)  The helpful error
   messages must still be provided when Emacs starts.

772 773 774 775 776

-- Implement terminal deletion, i.e., deleting local frames, closing
   the tty device and restoring its previous state without exiting

778 779
   (Done, but at the moment only called when an error happens during
   initialization.  There is a memory corruption error around this
   somewhere.)  (Update: now it is fully enabled.)

782 783 784 785 786
-- Implement automatic deletion of terminals when the last frame on
   that terminal is closed.


Karoly Lorentey's avatar
Karoly Lorentey committed
787 788 789 790 791
-- Restore tty screen after closing the terminal.

   (Done, we do the same as Emacs 21.2 for all terminals.)

-- 'TERM=dumb src/emacs' does not restore the terminal state.

Karoly Lorentey's avatar
Karoly Lorentey committed

795 796 797 798 799 800 801 802
-- C-g should work on secondary terminals.

   (Done, but the binding is not configurable.)

-- Deal with SIGHUP in Emacs and in emacsclient.  (After this, the
   server-frames may be removed from server.el.)

   (Done, nothing to do.  It seems that Emacs does not receive SIGHUP
   from secondary ttys, which is actually a good thing.)  (Update: I
   think it would be a bad idea to remove server-frames.)

-- Change emacsclient/server.el to support the -t argument better,
807 808 809 810
   i.e. automatically close the socket when the frame is closed.

   (Seems to be working OK.)

-- Fix mysterious memory corruption error with tty deletion.  To
812 813 814 815 816
   trigger it, try the following shell command:

	while true; do TERM=no-such-terminal-definition emacsclient -h; done

   Emacs usually dumps core after a few dozen iterations.  (The bug
   seems to be related to the xfreeing or bzeroing of
818 819 820
   tty_output.Wcm.  Maybe there are outside references to struct Wcm?
   Why were these vars collected into a struct before multi-tty

822 823 824 825
   (Done.  Whew.  It turned out that the problem had nothing to do
   with hypothetical external references to Wcm, or any other
   tty_output component; it was simply that delete_tty closed the
   filehandles of secondary ttys twice, resulting in fclose doubly
   freeing memory.  Utterly trivial matter.  I love the C's memory
827 828
   management, it puts hair on your chest.)

-- Support raw secondary terminals.  (Note that SIGIO works only on
   the controlling terminal.) Hint: extend read_input_waiting for
   multiple ttys and hopefully this will be fixed.

833 834 835 836
   (Done, it seems to have been working already for some time.  It
   seems F_SETOWN does work, after all.  Not sure what made it fail
   earlier, but it seems to be fixed (there were several changes
   around request_sigio, maybe one of them did it).
   read_input_waiting is only used in sys_select, don't change
   it.)  (Update: After adding X support, it's broken again.)
Karoly Lorentey's avatar
Karoly Lorentey committed
   (Update^2: No it isn't.) :-)

-- Find out why does Emacs abort when it wants to close its
Karoly Lorentey's avatar
Karoly Lorentey committed
   controlling tty.  Hint: chan_process[] array.  Hey, maybe
843 844
   noninterrupt-IO would work, too?  Update: no, there is no process
   for stdin/out.
Karoly Lorentey's avatar
Karoly Lorentey committed

846 847
   (Done.  Added add/delete_keyboard_wait_descriptor to
   term_init/delete_tty.  The hint was right, in a way.)

-- Issue with SIGIO: it needs to be disabled during redisplay.  See if
   fcntl kernel behaviour could be emulated by emacsclient.
Karoly Lorentey's avatar
Karoly Lorentey committed

   (Done.  Simply disabled the SIGIO emulation hack in emacsclient.)
Karoly Lorentey's avatar
Karoly Lorentey committed
   (Update: it was added back.)  (Update^2: and removed again.)

-- server.el: There are issues with saving files in buffers of closed
856 857 858 859 860
   clients.  Try editing a file with emacsclient -f, and (without
   saving it) do a delete-frame.  The frame is closed without
   question, and a surprising confirmation prompt appears in another

861 862 863 864
   (Done.  delete-frame now asks for confirmation if it still has
   pending buffers, and modified buffers don't seem to be deleted.)

-- emacsclient.el, server.el: Handle eval or file open errors when
   doing -t.


869 870
-- Make parts of struct tty_output accessible from Lisp.  The device
   name and the type is sufficient.

872 873 874
   (Done, see frame-tty-name and frame-tty-type.)

-- Export delete_tty to the Lisp environment, for emacsclient.

876 877
   (Done, see delete-tty.)

878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897
-- Get rid of the accessor macros in termchar.h, or define macros for
   all members.


-- Move device-specific parameters (like costs) commonly used by
   device backends to a common, device-dependent structure.

   (Done.  See struct display_method in termhooks.h.)

-- Fix X support.

   (Done.  Well, it seems to be working.)

-- Allow simultaneous X and tty frames.  (Handling input could be
   tricky.  Or maybe not.)

   (Done.  Allowed, that is.  It is currently extremely unstable, to
   the point of being unusable.  The rif variable causes constant
   core dumps.  Handling input is indeed tricky.)

-- Rewrite multi-tty input in terms of MULTI_KBOARD.

901 902 903
   (Done.  In fact, there was no need to rewrite anything, I just
   added a kboard member to tty_display_info, and initialized the
   frame's kboard from there.)

905 906 907 908 909 910 911
-- Fix rif issue with X-tty combo sessions.  IMHO the best thing to do
   is to get rid of that global variable (and use the value value in
   display_method, which is guaranteed to be correct).

   (Done, did exactly that.  Core dumps during combo sessions became
   much rarer.  In fact, I have not yet met a single one.)

912 913 914 915
-- Add multi-tty support to talk.el.


916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949
-- Clean up the source of emacsclient.  It is a mess.

   (Done, eliminated stupid proxy-pty kludge.)

-- Fix faces on tty frames during X-tty combo sessions.  There is an
   init_frame_faces call in init_sys_modes, see if there is a problem
   with it.

   (Done, there was a stupid mistake in
   Ftty_supports_face_attributes_p. Colors are broken, though.)

-- C-x 5 2, C-x 5 o, C-x 5 0 on an emacsclient frame unexpectedly
   exits emacsclient.  This is a result of trying to be clever with

   (Fixed, added delete-tty-after-functions, and changed server.el to
   use it.)

-- Something with (maybe) multi-keyboard support broke function keys
   and arrows on ttys during X+tty combo sessions.  Debug this.

   (I can't reproduce it, maybe the terminal type was wrong.)

-- Fix input from raw ttys (again).

   (Now it seems to work all right.)

-- During an X-tty combo session, a (message "Hello") from a tty frame
   goes to the X frame.  Fix this.

   (Done.  There was a safeguard against writing to the initial
   terminal frame during bootstrap which prevented echo_area_display
   from working correctly on a tty frame during a combo session.)

-- If there are no frames on its controlling terminal, Emacs should
Karoly Lorentey's avatar
Karoly Lorentey committed
   exit if the user presses C-c there.
952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971

   (Done, as far as possible.  See the SIGTERM comment in
   interrupt_signal on why this seems to be impossible to solve this
   in general.)

-- During an X session, Emacs seems to read from stdin.  Also, Emacs
   fails to start without a controlling tty.

   (Fixed by replacing the troublesome termcap display with a dummy
   bootstrap display during bootstrap.

-- Do tty output through struct display, like graphical display


-- Define an output_initial value for output_method for the initial
   frame that is dumped with Emacs.  Checking for this frame (e.g. in
   cmd_error_internal) is ugly.

   (Done, breaking interactive temacs.)
973 974 975 976 977

-- The command `emacsclient -t -e '(delete-frame)'' fails to exit.


978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998
-- frame-creation-function should always create a frame that is on the
   same display as the selected frame.  Maybe frame-creation-function
   should simply be removed and make-frame changed to do the right

   (Done, with a nice hack.  frame-creation-function is now frame-local.)

-- Fix C-g on raw ttys.

   (Done.  I disabled the interrupt/quit keys on all secondary
   terminals, so Emacs sees C-g as normal input.  This looks like an
   overkill, because emacsclient has extra code to pass SIGINT to
   Emacs, so C-g should remain the interrupt/quit key on emacsclient
   frames.  See the next entry why implementing this distinction would
   be a bad idea.)

-- Make sure C-g goes to the right frame with ttys.  This is hard, as
   SIGINT doesn't have a tty parameter. :-(

   (Done, the previous change fixes this as a pleasant side effect.)

999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028
-- I have seen a case when Emacs with multiple ttys fell into a loop
   eating 100% of CPU time.  Strace showed this loop:

	getpid()                                = 30284
	kill(30284, SIGIO)                      = 0
	--- SIGIO (I/O possible) @ 0 (0) ---
	ioctl(6, FIONREAD, [0])                 = -1 EIO (Input/output error)
	ioctl(5, FIONREAD, [0])                 = -1 EIO (Input/output error)
	ioctl(0, FIONREAD, [0])                 = 0
	sigreturn()                             = ? (mask now [])
	gettimeofday({1072842297, 747760}, NULL) = 0
	gettimeofday({1072842297, 747806}, NULL) = 0
	select(9, [0 3 5 6], NULL, NULL, {0, 0}) = 2 (in [5 6], left {0, 0})
	select(9, [0 3 5 6], NULL, NULL, {0, 0}) = 2 (in [5 6], left {0, 0})
	gettimeofday({1072842297, 748245}, NULL) = 0

   I have seen something similar with a single X frame, but have not
   been able to reproduce it for debugging.

   Update: This may have been caused by checking for nread != 0
   instead of nread > 0 after calling read_socket_hook in

   (Fixed.  This was caused by unconditionally including stdin in
   input_wait_mask in init_process.  The select call in
   wait_reading_process_input always returned immediately, indicating
   that there is pending input from stdin, which nobody read.

   Note that the above strace output seems to be an unrelated but
   similar bug.  I think that is now fixed.)

1030 1031 1032 1033 1034 1035 1036 1037 1038
-- Exiting Emacs while there are emacsclient frames doesn't restore the
   ttys to their default states.

   (This seems to be fixed by some previous change.)

-- Allow opening an X session after -nw.


1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049
-- Fix color handling during tty+X combo sessions.  (It seems that tty
   sessions automatically convert the face colors to terminal colors
   when the face is loaded.  This conversion must happen instead on
   the fly in write_glyphs, which might be problematic, as color
   approximation is currently done in lisp (term/tty-colors.el).)
   (Update: hm, colors seem to work fine if I start emacs with -nw and
   then create an X frame.  Maybe it's just a small buglet somewhere.)

   (Seems to be fixed.  The problem was in startup.el, it did not
   initialize tty colors when the initial window system was

1051 1052 1053 1054 1055
-- emacs -nw --eval '(y-or-n-p "Foobar")' segfaults.  (Reported by
   Romain Francoise)

   (Fixed, there was a keyboard initialization problem.)

Karoly Lorentey's avatar
Karoly Lorentey committed
1056 1057 1058 1059 1060
-- Fix interactive use of temacs.  There are face-related SEGVs, most
   likely because of changes in realize_default_face, realize_face.


1061 1062 1063 1064 1065
-- Don't exit Emacs when the last X connection fails during a
   multi-display session.


1066 1067 1068 1069 1070 1071
-- Dan Nicolaescu noticed that starting emacsclient on the same
   terminal device that is the controlling tty of the Emacs process
   gives unexpected results.


1072 1073 1074 1075 1076 1077 1078
-- Istvan Marko reported that Emacs hang on ttys if it was started
   from a shell script.

   (Fixed.  There was a bug in the multi-tty version of
   narrow_foreground_group.  tcsetpgrp blocks if it is called from a
   process that is not in the same process group as the tty.)

1079 1080 1081 1082
-- emacsclient -t from an Emacs term buffer does not work, complains
   about face problems.  This can even lock up Emacs (if the recursive
   frame sets single_kboard).  Update: the face problems are caused by
   bugs in term.el, not in multi-tty.  The lockup is caused by
Karoly Lorentey's avatar
Karoly Lorentey committed
   single_kboard mode, and is not easily resolvable.  The best thing to
1084 1085 1086 1087 1088 1089
   do is to simply refuse to create a tty frame of type `eterm'.

   (Fixed, changed emacsclient to check for TERM=eterm.  The face
   complaints seem to be caused by bugs in term.el; they are not
   related to multi-tty.)

1090 1091 1092 1093 1094 1095 1096 1097 1098 1099
-- Find out the best way to support suspending Emacs with multiple
   ttys.  My guess: disable it on the controlling tty, but from other
   ttys pass it on to emacsclient somehow.  (It is (I hope) trivial to
   extend emacsclient to handle suspend/resume.  A `kill -STOP' almost
   works right now.)

   (Done.  I needed to play with signal handling and the server
   protocol a bit to make emacsclient behave as a normal UNIX program
   wrt foreground/background process groups.)

Karoly Lorentey's avatar
Karoly Lorentey committed
1100 1101 1102 1103 1104 1105 1106
-- There is a flicker during the startup of `emacs -nw'; it's as if
   the terminal is initialized, reset and then initialialized again.
   Debug this.  (Hint: narrow_foreground_group is called twice during

   (This is gone.)

1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117
-- Robert Chassell has found serious copy-paste bugs with the
   multi-tty branch.  There seem to be redisplay bugs while copying
   from X to a terminal frame.  Copying accented characters do not
   work for me.

   (Patch-124 should fix this, by changing the interprogram-*-function
   variables to be frame-local, as suggested by Mark Plaksin
   (thanks!).  I think that the redisplay bugs are in fact not bugs,
   but delays caused by single_kboard --> perhaps MULTI_KBOARD should
   be removed.)

1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137
-- frame-creation-function was removed, which might be a bad idea.
   Think up a compatible solution.

   (It was an internal interface that may be changed when necessary.)

-- Change Lisp code not to (getenv "TERM"); use the `tty-type' frame
   parameter or the frame-tty-type function instead.  (M-x tags-search
   "TERM" helps with this.)  Update: Actually, all getenv invocations
   should be checked for multi-tty compatibility, and an interface
   must be implemented to get the remote client's environment.

   (Done.  Only getenv calls in lisp/term/*.el were changed; other
   calls should be mostly left as they are.)

-- Add an elaborate mechanism for display-local variables.  (There are
   already a few of these; search for `terminal-local' in the Elisp

   (Not needed.  Display-local variables could be emulated by
   frame-local variables.)

Karoly Lorentey's avatar
Karoly Lorentey committed
1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149
-- Emacs assumes that all terminal frames have the same locale
   settings as Emacs itself.  This may lead to bogus results in a
   multi-locale setup. (E.g., while logging in from a remote client
   with a different locale.)
   (Update after new bugreport by Friedrich Delgado Friedrichs: 
   (at least) the structs terminal_coding and keyboard_coding in
   coding.c must be moved to struct display, and the Lisp interface
   [set-]keyboard-coding-system must be adapted for the change.)

   (Fixed.  Emacs now uses the locale settings as seen by the
   emacsclient process for server tty frames.)
   (Update: Not really; Vlocale_coding_system is still global.)
1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201

-- Make `struct display' accessible to Lisp programs.  Accessor functions:

	(displayp OBJECT):  Returns t if OBJECT is a display.
		=> Implemented as display-live-p.

	(display-list):  Returns list of currently active displays.
		=> Implemented.

	(selected-display):  Returns the display object of the selected frame.
		=> Not strictly necessary, but implemented anyway.

	(frame-display FRAME):  Returns the display object of FRAME.
	        => Implemented.

	(display-frames DISPLAY):  Returns a list of frames on DISPLAY.
		=> Already implemented, see frames-on-display-list.

	(display-type DISPLAY):  Returns the type of DISPLAY, as a
		symbol.  (See `framep'.)
		=> Implemented as display-live-p.

	(display-device DISPLAY): Returns the name of the device that
		DISPLAY uses, as a string.  (E.g: "/dev/pts/16", or
		=> Implemented as display-name.


   See next issue why this is necessary.

   (Update: The consensus on emacs-devel seems to be to do this via
   integer identifiers.  That's fine by me.)


-- The following needs to be supported:

	$ emacsclient -t
	$ emacsclient -t
		(This fails now.)

   The cleanest way to solve this is to allow multiple displays on the
   same terminal device; each new emacsclient process should create
   its own display.  As displays are currently identified by their
   device names, this is not possible until struct display becomes
   accessible as a Lisp-level object.


1202 1203 1204 1205 1206 1207 1208
-- Miles Bader suggests that C-x C-c on an emacsclient frame should
   only close the frame, not exit the entire Emacs session.  Update:
   see above for a function that does this.  Maybe this should be the
   new default?  

   (Done.  This is the new default.  No complaints so far.)

1209 1210 1211 1212
-- Clean up the frame-local variable system.  I think it's ugly and
   error-prone.  But maybe I just haven't yet fully understood it.

   (Nothing to do.  It doesn't seem ugly any more.  It's rather clever.)

1214 1215 1216 1217 1218 1219 1220 1221 1222
-- Support multiple character locales.  A version of
   `set-locale-environment' needs to be written for setting up
   display-local settings on ttys.  I think calling
   set-display-table-and-terminal-coding-system and
   set-keyboard-coding-system would be enough.  The language
   environment itself should remain a global setting.

   (Done, by an ugly hack.)

1223 1224 1225 1226 1227 1228 1229