>>>> "Per" == Per Abrahamsen
Per> sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
> As long as defcustom'ing doesn't zap the initial value (I
> the customize semantics exactly), it's absolutely fine with me. The
> startup code is just that---code to be run at startup.
Per> It doesn't, but:
Per> - Custom will tell the user that the variable has changed outside
Per> customize when he tries to customize it. This may confuse the
Per> - When the user saves the variable, it will overwrite the value from
Per> the startup code. Not add to it. This means he will be bound to a
Per> specific location for the XEmacs distribution.
Per> In general, my advice is to split such user options in two. One for
Per> the standard (computed or large default) part, and one for the user
Per> specified part.
That's exactly the plan for all paths/directory lists for 21.2.
Cheers =8-} Chipsy
Friede, Völkerverständigung und überhaupt blabla