Hrvoje Niksic <hniksic(a)srce.hr> writes:
Just for the record, I agree with this. Even without
`.xemacs/',
custom-file should default to something other than `.emacs'. To do
so, we must make sure that:
1) Old `.emacs' files with custom options are handled gracefully;
2) The new `.xemacs-custom' file is loaded automatically, after
`.emacs'.
I suggest not using an .xemacs-custom file but use .xemacs/options.el
even if we do not use .xemacs/init.el, because
1. We already have been doing it (unintentionnaly) and it seems to
work.
2. Having an .xemacs-custom file is making the (eventual) migration to
.xemacs/ based system even more difficult as it is yet another file
to care for.
3. We have .xemacs anyway for the package system.
Jan