Re: XEmacs 21.0 and the options menu
Jan Vroonhof <vroonhof(a)math.ethz.ch> writes:
Didier Verna <verna(a)inf.enst.fr> writes:
> The options menu is ported to Custom, but we have no upgrade function >
from the old format to the new one. For most people, the options file is >
loaded *after* .emacs, but XEmacs 21.0 will save custom stuff in
.emacs. This > will lead to problems when people will use again the options
menu: their new > settings will be saved in .emacs, but won't have any
effect for the next > sessions since they will be overriden by the options
file.
Not true. At least not if you do not mix versions. Note that the options
loading code generated by 20.4 does check that the version is = 20 and
therefore the options file never gets loaded under 21.x
Yup. So people upgrading will believe they lost their options
setting. Not much better :-( If we don't find a better solution, this should
at least be documented in the NEWS file.
Even if this was not the case or if you want to support mixing
version
you can get away by redefining load-options-file.
The problem is more about options saving than options loading.
I thought about writing a migrate.el to convert the old options to
custom but it seems to me it is not worth it. Most of the options can
simply be copied by loading the old options file by hand once and then
doing a save-options.
Wrong. The options menu saving button calls
customize-save-customized. If you load the options from the old file, the
options will actually be changed outside Custom, and thus the save button will
not save them.
--
/ / _ _ Didier Verna http://www.inf.enst.fr/~verna/
- / / - / / /_/ / E.N.S.T. INF C214 mailto:vernaļ¼ inf.enst.fr
/_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72
75634 Paris cedex 13 Fax. (33) 01 45 81 31 19