Colin Rafferty <colin(a)xemacs.org> writes:
However, giving it a little thought, I think the idea was that we
were trying to stop having XEmacs modify ~/.emacs. ~/.emacs is for
the user to fool with, and ~/.custom.emacs is for XEmacs to fool
with.
In general, I think this is still the right idea.
It was the right idea, and that's what we're trying to achieve now.
The part that was wrong was the use of `custom-file' for disabled
commands as well as Custom. Either that file should have remained
reserved for Custom's private use, or the concept of automatically
generated startup Lisp should have been expanded to cover both Custom
and disabled commands.
This is not a big problem; it can be worked around. I just quoted the
ChangeLog to show that the use of custom-file for disabled commands
was added as an after-thought.