RE: Scratch buffer annoyance

[Drew Adams]

> >>     > ! (defcustom initial-buffer nil
> >>
> >> That variable name is misleading because the value is not a buffer.
> >> Please change the variable name to one that fits the meaning.
> >
> > The name `initial-buffer' means what the current buffer the user gets
> > after startup: a buffer with the home directory, a buffer with some
> > specified file, the *scratch* buffer, or the buffer with startup screen.
> >
> > I don't see a better name.  Maybe, `initial-display-buffer' or
> > `initial-current-buffer'?
>
> initial-visit maybe?


1. `visit-on-startup' (the original proposal).

Or `show-on-startup' if you don't like "visit". As David pointed out,
"startup" is clear and is consistently used to describe the startup stuff in
doc strings. If you reject "startup" and insist on "initial", then
`visit-initially' or `show-initially'.


2. Many newbies won't even know at this point what a buffer is. "*scratch*"
won't mean much to them either, but calling it a "Lisp buffer" or, better, a
"scratch Lisp buffer" will give them an idea what it is.


3. And the verbs "create", "visit", and "read" are not needed. It's obvious
what you do with each of these: new file, directory, scratch buffer,
tutorial, FAQ, manual.

So, as I suggested earlier, keep it simple:

>  [New File]
>  [Directory]
>  [Scratch Lisp Buffer]
>  [Tutorial]
>  [FAQ]
>  [Manual]
>  [Customize Startup Display]