Close .emacs file after customization?

[burton@openprivacy.org (Kevin A. Burton (burtonator))]

If the user is running with a fresh Emacs instance (no open buffers), then
customizes a variable, the .emacs file is left as an open buffer.

Why is this?  Is there a reason?

It would seem that we should pollute the buffer list if the .emacs file hasn't
already been opened manually.

This isn't a theoretical problem.  I am trying to run multiple .emacs versions
and I want to maintain the same customization options across Emacs instances.

If I open the .emacs file in one instance, customize it, then do the same in
another instance, they both have an open copy of the buffer and there are race
conditions as to which emacs version should be modifying the file.

Can we just fix customization to close the .emacs file after it modifies it?

Kevin

-- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burton@peerfear.org )
             Location - San Francisco, CA, Cell - 415.595.9965
           AIM - sfburtonator,  Web - http://www.peerfear.org/
        GPG fingerprint: 4D20 40A0 C734 307E C7B4  DCAA 0303 3AC5 BD9D 7C4D
         IRC - openprojects.net #infoanarchy | #p2p-hackers | #reptile

Who wants to be responsible?  Every time something goes wrong they say 'who's
responsible for this?'
  -- Jerry Seinfeld