Ben Wing <ben(a)666.com> writes:
PRINCIPLE #3: *ALL* generated stuff should be loaded before any
stuff. This way the user can override the generated settings. Although in the
case of customize, it may work when the custom stuff is at the end of the init
file, it surely won't work for arbitrary code fragments (which typically do
or the like).
I used to have the customize stuff at the end of .emacs and found that
this can cause problems:
Somewhere above the customize stuff I did read the buffers from the
previous XEmacs session using
when there was a html-file among the files loaded by `desktop-read', I
was asked for my e-mail-address and subsequently asked whether I would
like to make this permanent. When answering `y', all customizations
It looks like the customizations had not yet been loaded (because they
followed below in .emacs), therefore customize thought that nothing was
customized and created a `custom-set-variables' statement containing
'(user-mail-address "mike.fabian(a)gmx.de" t)
All other customizations were gone.
I was happy to have a backup.
After that I moved the customize stuff to the top of my .emacs.
This solves the problem.
Mike Fabian <mike.fabian(a)gmx.de> <mike(a)nozomi.rhein-neckar.de>