Re: how could the mighty emacs lack --fullscreen ?

[Richard Stallman]

    It would make the initial frame move about less when first created.  For
    instance, if one has 
     (menu-bar-mode -1)
    or (assuming the fullscreen patch):
     (setq initial-frame-alist (list (cons 'fullscreen 'fullheight)))

    in .emacs, the window first appears with the default size, and after that 
it is
    modified.  This is no big deal, it just looks "jumpy".

If instead of displaying the frame and then changing it,
Emacs displayed a splash screen and then replaced it,
why would that be any less "jumpy"?  That is what I don't understand.
Why does it matter whether what appears initially is the
initial frame or a splash screen?

    Yes, perhaps all of this can be made in .Xdefaults instead.  I
    think there is an advantage if they both behave the same.  After
    all, customize is easy to use from within emacs.  The help one
    gets from apropos and C-h C-f also makes it a bit easier to find
    the .emacs setting than the X resource.

Perhaps Custom should update .Xdefaults when you change certain
variables.  What do people think of that?