"Stephen J. Turnbull" <stephen(a)xemacs.org> writes:
David Kastrup writes:
> I could have just quit after you calling me "just paranoid" instead of
> giving an explicit example of a problematic case.
I didn't say you weren't helpful, just that you could try harder than
than that last message, which was unproductive in all respects.
Eg, I don't *know* that (setq custom-file ...) *is* a problem; it
seems quite likely to me that Mike tests for that and does something
about it in the migration process. But I don't *know* that he did, so
I conceded you have a point.
Not really: It migrates the custom settings out of the file pointed to
by `custom-file' - it just uses custom's API to do that. It does not
fiddle with the setting of `custom-file' itself (which presumable also
got migrated). It does however change the value of custom-file *in the
session where the migration happened*.
So this is not entirely satisfactory: Doing the right thing would be to
detect that `custom-file' points somewhere else, and then leave the
custom settings alone. Does that sound right?
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
XEmacs-Beta mailing list