David Kastrup writes:
It is likely a good idea to refuse even this if variables like
custom-file, user-init-file, user-emacs-directory are changed from their
default. At least if XEmacs interprets those variables.
Because otherwise loading the copied .emacs file is likely to ultimately
result in writes to original files anyway.
That's pure paranoia with no foundation in reality, David. Once those
variables are set (all of the logic for finding the init file is
hard-coded in the initialization), ~/.emacs is just another file to
XEmacs. There is no evidence whatsoever that (once configured) XEmacs
will make the mistake of setting user-init-file to "~/.emacs", in at
least 15 years of experience with init.el.
It's also true that the *user* may become confused *if* they try to
edit ~/.emacs in XEmacs. Again, that's perverse, not an easily-made
mistake, and XEmacs should not try to second-guess the user.
XEmacs-Beta mailing list