Rodney Sparapani writes:
Let me jump in. So, RHEL "helpfully" creates an .emacs for
Hang on a sec. Are you sure there was a .emacs *before* you started
XEmacs? It's possible that there's a bug and XEmacs decides that a
non-existent file needs to be migrated or something silly like that.
It's also possible that RHEL's .emacs is a dummy file filled with
sample code that is commented out or something like that.
(Don't worry about it if you're not sure, Jerry probably knows.)
You were right earlier. I did save the customizations just like you
do in Issue 411. But, since I didn't migrate, the customizations
went into .emacs Since I am not a heavy Emacs customize user, that
caught me off guard as well; I didn't know Emacs did that.
I don't know if it does any more.
But, I would recommend not looking at .emacs at all and not attempt
migrate it. That's what SXEmacs does as I understand it and I think
that's best. And, that would prevent some of these mis-conceptions.
This code was written in 1999 or 2000, I think, and at that time
XEmacs was much more compatible with GNU Emacs. Then it made a lot of
sense for halfway experts to try to share, and at least some sense to
try to help them out in the migration process. Now, even though
there's probably some sense to sharing for *some* people, it probably
should be 100% manual.
XEmacs-Beta mailing list