Re: Close .emacs file after customization?

[David Masterson]

>>>>> Richard Stallman writes:

>     You will get a warning if customize *does not* kill the .emacs buffer
>     after saving customization, which is currently the case, but that is
>     precisely what the original poster wanted to change.

> If Emacs already has a buffer visiting .emacs, and that file has
> changed on disk, visiting it again will ask whether to reread the
> file.  The only advantage of killing the buffer is that you won't
> have to answer that question.  Is that a major advantage?

The other advantage is that it no longer is in memory, but that may
not be major.  I think the real question, though, should be is there a
major advantage to *not* killing the buffer.  This becomes more
important when you remember that it's not about killing the .emacs
buffer, but rather the custom-file buffer.

> We could make Custom kill the buffer if it didn't exist before
> Custom created it.

That's probably preferable to prevent confusion.

-- 
David Masterson                David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA