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

5 6 7
The goal of this branch is to implement support for opening multiple,
different tty devices and simultaneous X and tty frames from a single
Emacs session.
8

9 10 11 12 13 14 15 16 17 18 19 20 21 22
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 console.
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.

23 24 25 26 27
WHO IS DOING IT
---------------

I'm Károly Lőrentey.  My address: lorentey@elte.hu.

28
Comments, bug reports, suggestions and patches are welcome!
29

30
Retrieving the latest version of the branch:
31 32

	tla register-archive lorentey@elte.hu--2004 http://lorentey.web.elte.hu/arch/2004/
33
	tla get lorentey@elte.hu--2004/emacs--multi-tty <directory>
34

35 36 37 38 39
(I use a recent arch development snapshot, but any of the released
versions of arch will do fine, I think.)

If you don't have arch, the branch has a homepage from which you can
download conventional patches against Emacs CVS HEAD:
40

41
	http://lorentey.web.elte.hu/project/emacs.html
42

43 44 45 46 47 48 49 50 51
If you want to be notified of new revisions, sign up to the
multi-tty@listbox.elte.hu mailing list by visiting the
below homepage and following its instructions.

	https://listbox.elte.hu/mailman/listinfo/multi-tty

Please note that the multi-tty mailing list is read-only, and is
reserved for automatic commit messages.  Discussion about the branch
and bug reports should be sent directly to me (lorentey@elte.hu), or
Karoly Lorentey's avatar
Karoly Lorentey committed
52 53 54
to the emacs-devel@gnu.org mailing list.  (I hope to merge my branch
into CVS HEAD reasonably soon, so I don't want to set up an elaborate
development infrastructure for the multi-tty branch.)
55

56 57 58
STATUS
------

59 60 61 62
The branch is now very stable and almost full-featured. I hope the
major problems were fixed.  (It still needs testing on other
architectures, though.)  Both multiple tty device support and
simultaneous X and tty frame support works fine.  Emacsclient has been
Karoly Lorentey's avatar
Karoly Lorentey committed
63 64
extended to support opening new tty and X frames.  It has been changed
open new Emacs frames by default.
65 66

Please let me know if you find any bugs in this branch.
67

68 69 70
HOW TO COMPILE AND TEST
-----------------------

Karoly Lorentey's avatar
Karoly Lorentey committed
71 72
To try out the multi-tty branch, compile and run the multi-tty branch
with the following commands:
73

Karoly Lorentey's avatar
Karoly Lorentey committed
74
        find -name "*.elc" | xargs rm   # Delete leftover stuff
75 76
   	mkdir +build
	cd +build
77
	../configure <your favourite options>
78
	make bootstrap
79
	src/emacs -nw		# You can also try without -nw
80
	M-x server-start
81

82 83
and then (from a shell prompt on another terminal) start emacsclient
with
Karoly Lorentey's avatar
Karoly Lorentey committed
84 85
	lib-src/emacsclient /optional/file/names...
or
86
	lib-src/emacsclient -t /optional/file/names...
87

Karoly Lorentey's avatar
Karoly Lorentey committed
88
You'll hopefully have two fully working, independent frames on
89
separate terminals. The new frame is closed automatically when you
Karoly Lorentey's avatar
Karoly Lorentey committed
90 91 92
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
devices.
93

94 95 96
Creating new frames on the same tty with C-x 5 2 works, and they
behave the same way as in previous Emacs versions.  If you exit emacs,
all terminals should be restored to their previous states.
97

98 99
This is work in progress, and probably full of bugs.  You should
always run emacs from gdb, so that you'll have a live instance to
100
debug if something goes wrong.  Please send me your bug reports.
Karoly Lorentey's avatar
Karoly Lorentey committed
101

102 103 104 105 106 107 108 109 110 111 112 113 114 115
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
normal work.  This way 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.  As long as the server that runs
your Emacs remains up, all your buffers remain exactly as they were
before the crash, and you can continue working as if nothing had
happened.  (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.)

(I am thinking about introducing a --daemon option to get rid of the
above screen dependency.)

116
Problems:
117

118 119 120
	* Mac, Windows and DOS support is broken, probably doesn't
	  even compile -- this will be solved later.

Karoly Lorentey's avatar
Karoly Lorentey committed
121
	* Only tested on my GNU/Linux box, Solaris 8 and FreeBSD.
122 123 124 125 126 127

NEWS
----

For the NEWS file:

128
** Support for multiple terminal devices has been added.
129

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

133 134
*** You can test for the presence of multiple terminal support by
    testing for the `multi-tty' feature.
135

136
*** Emacsclient has been extended to support opening a new terminal
Karoly Lorentey's avatar
Karoly Lorentey committed
137 138 139
    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.
140

141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160
*** A make-frame-on-tty function has been added to make it easier to
    create frames on new terminals.

*** New functions: frame-tty-name, frame-tty-type for accessing
    terminal parameters, and delete-tty for closing the terminal
    device.

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


** Support for simultaneous graphical and terminal frames has been
   added.

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

*** The `window-system' variable has been made frame-local.

*** The new `initial-window-system' variable contains the
    `window-system' value for the first frame.
161

162 163 164 165 166 167
THANKS
------

The following is an (incomplete) list of people who have contributed
to the project by testing, bug reports, and suggestions.  Thanks!

168
Robert J. Chassell <bob at rattlesnake dot com>
169
Romain Francoise <romain at orebokech dot com>
170
Ami Fischman <ami at fischman dot org>
171
Istvan Marko <mi-mtty ar kismala dot com>
172
Dan Nicolaescu <dann at ics dot uci dot edu>
Karoly Lorentey's avatar
Karoly Lorentey committed
173
Gergely Nagy <algernon at debian dot org>
Karoly Lorentey's avatar
Karoly Lorentey committed
174
Mark Plaksin <happy at mcplaksin dot org>
175
Francisco Borges <borges at let dot rug dot nl>
Karoly Lorentey's avatar
Karoly Lorentey committed
176
Frank Ruell <stoerte at dreamwarrior dot net>
Karoly Lorentey's avatar
Karoly Lorentey committed
177
and many others.
178

Karoly Lorentey's avatar
Karoly Lorentey committed
179 180
Richard Stallman was kind enough to review an earlier version of my
patches.
181

182 183 184 185 186
CHANGELOG
---------

See arch logs.

187 188
THINGS TO DO
------------
189

190 191 192 193 194 195 196 197 198 199 200
** frame-creation-function was removed, which might be a bad idea.
   Think up a compatible solution.

** make-frame does not correctly handle extra parameters in its
   argument:

	(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
201 202 203 204
** 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)?

Karoly Lorentey's avatar
Karoly Lorentey committed
205 206 207 208 209
** 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.)

Karoly Lorentey's avatar
Karoly Lorentey committed
210 211 212 213
** 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
214 215
   Nicolaescu.)  (Update: selecting a region with the mouse enables
   single_kboard under X.  This is very confusing.)
Karoly Lorentey's avatar
Karoly Lorentey committed
216

217
** Change Lisp code not to (getenv "TERM"); use the `tty-type' frame
Karoly Lorentey's avatar
Karoly Lorentey committed
218 219 220 221
   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.
222 223 224 225 226

** The terminal customization files in term/*.el tend to change global
   parameters, which may confuse Emacs with multiple displays.  Change
   them to tweak only frame-local settings, if possible.

Karoly Lorentey's avatar
Karoly Lorentey committed
227 228 229
** 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''
Karoly Lorentey's avatar
Karoly Lorentey committed
230
   options.  Patches are welcome.) :-)
Karoly Lorentey's avatar
Karoly Lorentey committed
231 232 233 234 235

** 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
   implement.
236

Karoly Lorentey's avatar
Karoly Lorentey committed
237 238 239 240
** 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.

Karoly Lorentey's avatar
Karoly Lorentey committed
241 242 243
** Miles Bader suggests that C-x C-c on an emacsclient frame should
   only close the frame, not exit the entire Emacs session.

244
** Make `struct display' accessible to Lisp programs.  Accessor functions:
245

246
	(displayp OBJECT):  Returns t if OBJECT is a display.
247

Karoly Lorentey's avatar
Karoly Lorentey committed
248 249
	(display-list):  Returns list of currently active displays.

250 251 252 253 254 255 256 257 258 259 260 261 262
	(selected-display):  Returns the display object of the selected frame.

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

	(display-frames DISPLAY):  Returns a list of frames on DISPLAY.

	(display-type DISPLAY):  Returns the type of DISPLAY, as a
		symbol.  (See `framep'.)

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

Karoly Lorentey's avatar
Karoly Lorentey committed
263 264
	etc.

265 266 267 268 269 270 271 272 273 274 275 276 277 278
   See next issue why this is necessary.

** The following needs to be supported:

	$ emacsclient -t
		C-z
	$ 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.
279 280 281 282 283

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

284 285 286 287 288 289 290
** 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.

** 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.

291
** Move baud_rate to struct display.
292 293 294

** 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
295
   later, with emacsclient.)
296

297 298 299 300
** Fix Mac support (I can't do this 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.
301

302 303 304 305
** Fix W32 support (I can't do this myself).  Note that the current
   state of W32-specific source files in the multi-tty tree are not
   useful; before starting work on W32 support, revert to pristine,
   pre-multi-tty versions.
306

307 308 309 310
** Fix DOS support (I can't do this 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.
311 312 313

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

Karoly Lorentey's avatar
Karoly Lorentey committed
314 315 316 317 318 319
** Understand Emacs's low-level input system (it's black magic) :-)
   What exactly does interrupt_input do?  I tried to disable it for
   raw secondary tty support, but it does not seem to do anything
   useful.  (Update: Look again. X unconditionally enables this, maybe
   that's why raw terminal support is broken again.  I really do need
   to understand input.)
320

321 322
** Maybe standard-display-table should be display-local.

323 324 325 326
DIARY OF CHANGES
----------------

(ex-TODO items with explanations.)
327

328
-- Introduce a new struct for terminal devices.
329

330
   (Done, see struct tty_output.  The list of members is not yet
331 332 333 334 335 336 337 338 339 340
   complete.)

-- 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'.)

341 342 343
-- Implement support for reading from multiple terminals.

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

347 348
   (Update: They do, now.)

349 350
   (Update2: After enabling X, they don't.)

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

354
   (Done, by trivially modifiying next_frame and prev_frame.)
355 356

-- Support different terminal sizes.
357

358 359 360 361 362
   (Done, no problem.)

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

363 364
   (Done.  We don't get automatic SIGWINCH for additional ttys,
   though.)
365 366 367

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

369 370
   (Done.  It's an ugly hack, needs more work.)

371 372
-- Redisplay must refresh the topmost frame on *all* terminals, not
   just the initial terminal.
373

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

376 377
-- Fix redisplay problems.

378 379
   (Done; it turned out that the entire Wcm structure must be moved
   inside tty_output.  Why didn't I catch this earlier?)
380 381 382 383 384 385 386 387 388 389

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

   (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.

390 391
   (Done, it was quite simple, the input event system already
   supported multiple frames.)
392 393 394 395

-- Fix SIGIO issue with secondary terminals.

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

Karoly Lorentey's avatar
Karoly Lorentey committed
399 400 401
   (Update: This is bullshit.  There is a read_input_waiting function,
   extend that somehow.)

402 403 404 405
   (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.)

406 407
   (Update^3: Not any more.)

408 409 410 411 412 413 414 415 416 417
-- Make make-terminal-frame look up the `tty' and `tty-type' frame
   parameters from the currently selected terminal before the global
   default.

   (Done.)

-- 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.

418
   (Done.  It was not fun.)
419 420

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

424 425 426 427 428
   (Done.)

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

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

434 435 436 437 438
-- Implement automatic deletion of terminals when the last frame on
   that terminal is closed.

   (Done.)

Karoly Lorentey's avatar
Karoly Lorentey committed
439 440 441 442 443
-- 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.
444

Karoly Lorentey's avatar
Karoly Lorentey committed
445
   (Done.)
446

447 448 449 450 451 452 453 454
-- 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
455
   from secondary ttys, which is actually a good thing.)  (Update: I
456
   think it would be a bad idea to remove server-frames.)
457

458
-- Change emacsclient/server.el to support the -t argument better,
459 460 461 462
   i.e. automatically close the socket when the frame is closed.

   (Seems to be working OK.)

463
-- Fix mysterious memory corruption error with tty deletion.  To
464 465 466 467 468
   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
469
   seems to be related to the xfreeing or bzeroing of
470 471 472
   tty_output.Wcm.  Maybe there are outside references to struct Wcm?
   Why were these vars collected into a struct before multi-tty
   support?)
473

474 475 476 477
   (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
478
   freeing memory.  Utterly trivial matter.  I love the C's memory
479 480
   management, it puts hair on your chest.)

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

485 486 487 488
   (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).
489
   read_input_waiting is only used in sys_select, don't change
490
   it.)  (Update: After adding X support, it's broken again.)
Karoly Lorentey's avatar
Karoly Lorentey committed
491
   (Update^2: No it isn't.) :-)
492

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

498 499
   (Done.  Added add/delete_keyboard_wait_descriptor to
   term_init/delete_tty.  The hint was right, in a way.)
500

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

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

507
-- server.el: There are issues with saving files in buffers of closed
508 509 510 511 512
   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
   frame.

513 514 515 516
   (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
517
   doing -t.
518

519
   (Done.)
520

521 522
-- Make parts of struct tty_output accessible from Lisp.  The device
   name and the type is sufficient.
523

524 525 526
   (Done, see frame-tty-name and frame-tty-type.)

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

528 529
   (Done, see delete-tty.)

530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549
-- Get rid of the accessor macros in termchar.h, or define macros for
   all members.

   (Done.)

-- 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.)
550

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

553 554 555
   (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.)
556

557 558 559 560 561 562 563
-- 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.)

564 565 566 567
-- Add multi-tty support to talk.el.

   (Done.)

568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601
-- 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
   delete-frame-functions.

   (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.)

602
-- If there are no frames on its controlling terminal, Emacs should
Karoly Lorentey's avatar
Karoly Lorentey committed
603
   exit if the user presses C-c there.
604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629

   (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
   backends.

   (Done.)

-- 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, broking interactive temacs.)

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

   (Fixed.)

630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650
-- 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
   thing.

   (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.)

651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680
-- 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
   read_avail_input.

   (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.)
681

682 683 684 685 686 687 688 689 690
-- 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.

   (Done.)

691 692 693 694 695 696 697 698 699 700 701
-- 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
   graphical.)
702

703 704 705 706 707
-- 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
708 709 710 711 712
-- Fix interactive use of temacs.  There are face-related SEGVs, most
   likely because of changes in realize_default_face, realize_face.

   (Fixed.)

713 714 715 716 717
-- Don't exit Emacs when the last X connection fails during a
   multi-display session.

   (Fixed.)

718 719 720 721 722 723
-- Dan Nicolaescu noticed that starting emacsclient on the same
   terminal device that is the controlling tty of the Emacs process
   gives unexpected results.

   (Fixed.)

724 725 726 727 728 729 730
-- 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.)

731 732 733 734
-- 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
735
   single_kboard mode, and is not easily resolvable.  The best thing to
736 737 738 739 740 741
   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.)

742 743 744 745 746 747 748 749 750 751
-- 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
752 753 754 755 756 757 758
-- 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
   startup.)

   (This is gone.)

759 760 761 762 763 764 765 766 767 768 769 770
-- 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.)


771

772
;;; arch-tag: 8da1619e-2e79-41a8-9ac9-a0485daad17d