Hrvoje> "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp&gt; writes: Excuse me; I meant "defaults to toggle if no defcustom is present." (At least `fgrep defcus packages/lisp/vm/*.el' doesn't turn up any.) In fact it claims the variable is a toggle even now that it has a list of strings as value. Hrvoje> No, what makes you think so? Can you name an example? The reason for the (unwarranted, perhaps) generalization is that I've had it happen to me before. The specific example is `vm-reply-ignored-reply-tos.' It started out nil, I tried to change it using custom, custom said ------------------------------------------------------------ Vm Reply Ignored Reply Tos: * [Toggle] off (nil) [State]: this option has not been changed with customize. Non-nil value should be a list of regular expressions that match * 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 will use the From header instead. ------------------------------------------------------------ I set it with setq, now custom says ------------------------------------------------------------ Vm Reply Ignored Reply Tos: * [Toggle] on (non-nil) [State]: this option has not been changed with customize. ... ------------------------------------------------------------ I get the latter result now that I've added the setq to ~/.vm in a fresh invocation of xemacs.