David Kastrup writes:
"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
> David Kastrup writes:
> > Sigh. When the user has
> > (setq custom-file "~/.emacs.d/custom.el")
> OK, you got me there. I didn't know Emacs supported that. (I also
> don't know that migration doesn't check for that.)
As long as XEmacs doesn't support it, there will be no problem.
XEmacs has supported it for longer than I've used XEmacs
(unfortunately for those who might get caught by it).
> > Well, but it seems you could use some practice
> No. That is never a good idea.
Well, you are second-guessing that he is smart enough to deal with all
problems himself, no questions asked.
I apologize for my dig at Emacs, and ask that you try to be more
helpful. Specifically, in general, this is the way Emacsen do things
(assuming that users can deal with problems), except that questions of
course may be asked. As contentious as inter-developer discussions
can be, in my experience (mostly on XEmacs channels) Emacs people are
very helpful to users. So I stand by my statement that second-guessing
the user is a bad idea.
The problem here is that because (unlike pretty much everything else
in Emacs!) Customize saves destructively without an option for
backup(s), you only get one chance to get it right. That's hard!
Unless Mike pops up to say it's already handled, I'll file one bug
aginst the migration process to check that standard init files (at the
moment, .emacs and custom.el) are not overwritten ever, and another
aginst Customize to do something about backups. And make sure they
get fixed soon (before the GPLv3 release if possible).
XEmacs-Beta mailing list