comparison README.multi-tty @ 53343:56e4b7166995

Make sure secondary frames are deleted when emacsclient quits. lisp/server.el (server-sentinel): Delete frame if alive. Fix delq invocation on server-frames. (server-process-filter, server-buffer-done): Fix delq invocation on server-frames. src/cm.c (cmputc): Abort on write error, see what happens. src/keyboard.c (read_avail_input): Do delete_tty on read errors. git-archimport-id: [e-mail]--2004/emacs--multi-tty--0--patch-21

53342:201b17b0f2e5

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

THINGS TO DO
------------

** Fix mysterious memory corruption error with tty deletion.  To
   trigger it, try the following shell command:

   The bug does not seem to happen if the error occurs before terminal
   initialization or if I comment out all xfree()s in delete_frame.
   Update: yes it does, although it is much rarer.  Or maybe it's
   another bug.

** Change emacsclient/server.el to support the -h argument better,
   i.e. automatically close the socket when the frame is closed.

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

** C-g should work on secondary terminals.

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

** Find out why does Emacs abort when it wants to close its
   controlling tty.  Hint: chan_process[] array.  Hey, maybe
   noninterrupt-IO would work, too?

   a backend-neutral per-device structure.

** Find out the best way to support suspending Emacs with multiple
   ttys.

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

** Do tty output through term_hooks, like all other display backends.

** Fix X support.

** Allow simultaneous X and tty frames.

53343:56e4b7166995

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

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

-- Change emacsclient/server.el to support the -h argument better,
   i.e. automatically close the socket when the frame is closed.

   (Seems to be working OK.)

THINGS TO DO
------------

** Fix mysterious memory corruption error with tty deletion.  To
   trigger it, try the following shell command:

   The bug does not seem to happen if the error occurs before terminal
   initialization or if I comment out all xfree()s in delete_frame.
   Update: yes it does, although it is much rarer.  Or maybe it's
   another bug.

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

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

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

** Find out why does Emacs abort when it wants to close its
   controlling tty.  Hint: chan_process[] array.  Hey, maybe
   noninterrupt-IO would work, too?

   a backend-neutral per-device structure.

** Find out the best way to support suspending Emacs with multiple
   ttys.

** Do tty output through term_hooks, like all other display backends.

** Fix X support.

** Allow simultaneous X and tty frames.