"Stefan Monnier" <monnier+lists.xemacs.beta/news/(a)rum.cs.yale.edu>
writes:
>>>>> "Andy" == Andy Piper
<andy(a)xemacs.org> writes:
> Does anyone know why custom-theme-set-variables (custom-set-variables)
> eval's its argument if now is t or if it has a default value.
IIRC, it's because the value can refer to other not-yet-loaded
variables (but variables which will be available when the
`defcustom' is actually run). I personally dislike this behavior
but Per seemed to think it was very important.
Per's "use case" (how I love that word) was something like:
(defcustom foo 10
"...")
(defcustom bar (* foo 3)
"...")
> Just trying to understand how I must set variables of this tye.
Just use sane commands, such as `setq', `add-hook', `push', ...
Normally a good advice. However, some developers have taken to adding
the setter "activation" methods to defcustoms, so you actually end up
with variables that do nothing when set with SETQ. Yuck.