RE: Scratch buffer annoyance

[Drew Adams]

>     1. Open to the *Customize Browser* buffer.  I think you're
>        proposing this.
>
>     2. Open to the *Customize Group* buffer (say *Customize Group:
>     convenience*).
>
>     3. Open to the *Customize Option: visit-on-startup* buffer.
>
> #3 sounds too specific.  Yes, it would enable someone to turn
> off the splash screen, but it wouldn't show that there are other
> possibilities.
>
> I think #2 is best.  It avoids unnecessary indirection while showing
> more than just one option.
>
>     Whenever the user asks to customize a single option, should
>     we just open the browser to a browser display that shows
>     that option or its group somewhere on it
>
> That's a different issue.  When the user specifically asks to customize
> one option, we should provide that option.  But here the user
> would be asking to "customize the startup screen".  That is NOT
> a request for one option.

It was at the time of the message you replied to - the single option was
`visit-on-startup'. However, since then, the discussion moved on.

My last proposal was that the link [Customize Startup Display] lead to
`customize-group' for a customize group `startup-display'. That buffer,
`*Customize Group: startup-display*' would show everything for the startup
display:

>   `visit-on-startup' [Hide Value] [Value Menu]
>   What to show/visit on startup.
>
>   `fancy-splash-screen' group: Go to Group
>   Fancy splash screen when Emacs starts.

With this approach, #2 above becomes the same thing: go to the customize
group, which would be `startup-display'.

Startup display deserves its own group because (1) most of the stuff in
group `initialization' has nothing to do with the startup display, and (2)
`visit-on-startup' is about the startup display, but it is not about the
`fancy-splash-screen'. This new goldilocks group is just right for
everything about the startup display. It doesn't include everything about
initialization, and it includes more than just the splash screen.