Re: the role of Custom in XEmacs (setting != saving)

Per Abrahamsen writes: Per> Basically everything you discuss is already implemented, and all the Per> proper distinctions are already in place. No they aren't. Indeed Custom already implements most of the stuff and in a pretty good manner. But as soon as Custom becomes the de-facto standard for saving options, it also _forces_ you to use its own setting method (the customization buffers) if you want your stuff to be saved. That's why I consider that the proper distinctions are not in place. Those distinctions won't be in place until we have figured out all the ways a user option could possibly be set, modified, whatever, and whether these modifications should have an impact on the value Custom will save. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19