Re: [proposed PATCH] Re: Customize and `nil' variables
"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
>>>>> "Hrvoje" == Hrvoje Niksic
<hniksic(a)srce.hr> writes:
Hrvoje> Yikes, this is because the docstring begins with
Hrvoje> "Non-nil", and confuses the Customize guessing code. Set
Hrvoje> (or change) `custom-guess-doc-alist' to work around the
Hrvoje> problem.
Thanks. In this case, isn't changing `custom-guess-name-alist'
better?
No, why?
In this case I'll try to convince Kyle to change the docstring. The
"non-nil" beginning is unnecessary, really. It could read, just as
nicely, as this:
Vm Reply Ignored Reply Tos: * [Toggle] off (nil)
[State]: this option has not been changed with customize.
list of regular expressions that matches * addresses that, if VM finds
in a message's Reply-To header, VM should ignore the Reply-To header
and not use it for replies. VM
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Ask not for whom the <CONTROL-G> tolls.