Re: 22.2.50; 23.0.60; customize-rogue is too long (emacs -Q)

[martin rudalics]

> | Default Frame Alist: [Show Value]
> |    State: HIDDEN, invoke "Show" in the previous line to show.
> |
> | Alist of default values for frame creation. [More]
> |
> | Initial Frame Alist: [Show Value]
> |    State: HIDDEN, invoke "Show" in the previous line to show.
> |    Alist of frame parameters for creating the initial X window frame. [More]
> |
> | Menu Bar Mode: [Hide Value] [Toggle]  on (non-nil)
> |    [State]: CHANGED outside Customize; operating on it here may be 
unreliable.
> |
> | Non-nil if Menu-Bar mode is enabled. [More]
> | Groups: [Frames]
> |
> | Pop Up Frame Function: [Show Value]
> |    State: HIDDEN, invoke "Show" in the previous line to show.
> |
> | Function to call to handle automatic new frame creation. [More]

You might want to consult the thread

"CHANGED outside Customize" in frames customization group

on emacs-devel starting 2007-12-29.


> | Same Window Buffer Names: [Show Value]
> |    State: HIDDEN, invoke "Show" in the previous line to show.
> |
> | List of buffer names that should appear in the selected window. [More]
> |
> | Same Window Regexps: [Show Value]
> |    State: HIDDEN, invoke "Show" in the previous line to show.
> |
> | List of regexps saying which buffers should appear in the selected window. 
[More]
> |

I would simply set these in window.el as soon as I moved them there.
What was the particular idea of those weird autoload cookies in the
first place?


> | Special Display Function: [Hide Value] special-display-popup-frame
> |    [State]: CHANGED outside Customize; operating on it here may be 
unreliable.
> |
> | Function to call to make a new frame for a special buffer. [More]
> | Groups: [Frames]

Will be fixed when moving `display-buffer' to window.el.