diff README.multi-tty @ 83362:c3dd82172ed1

Enforce the presence of `window-system' and `tty-type' frame parameters in all frames. * src/dispnew.c (init_display): Set up `window-system' and `tty-type' frame parameters in the initial tty frame. * src/frame.c (Fmake_terminal_frame): Look up the `tty-type' frame parameter, not `tty' when discovering the tty type of the new frame. Initialize `tty' and `tty-type' frame parameters in the new frame. git-archimport-id: [e-mail]--2004/emacs--multi-tty--0--patch-402

--- a/README.multi-tty	Wed Sep 07 23:17:07 2005 +0000
+++ b/README.multi-tty	Wed Sep 07 23:28:54 2005 +0000
@@ -398,13 +398,17 @@
    > The reason is that terminal-init-xterm calls
    > xterm-register-default-colors which calls (display-color-cells (selected-frame))
    > and probably `selected-frame' is not completely setup at that time. 
-   
+
 ** emacsclient --no-wait and --eval is currently broken.
 
 ** xt-mouse.el needs to be adapted for multi-tty.  It currently
    signals an error on kill-emacs under X, which prevents the user
    from exiting Emacs. (Reported by Mnemonikk on freenode.)
 
+** 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'.
+
 ** 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
@@ -1213,6 +1217,7 @@
    frame is selected.
 
    (Done.)
+   
 
 ;;; arch-tag: 8da1619e-2e79-41a8-9ac9-a0485daad17d