(require 'a)
(unload-feature 'a)
Now a-cus-var is not bound, but when I do M-x customize-option, I can
still select (with completion) a-cus-var and that gives me this
customization buffer:
I think the cleaner fix is to undo more of what the defcustom
did, so that the variable
Lute Kamstra <[EMAIL PROTECTED]> writes:
> unload-feature does not completely reverse the effects of defcustom.
>
> Consider this file:
>
> ,[ a.el ]
> | (defcustom a-cus-var 'a-value
> | "The documentation of `a-cus-var'.")
> | (provide 'a)
> `
>
> and do:
>
> (require 'a)
> (unload-fe
unload-feature does not completely reverse the effects of defcustom.
Consider this file:
,[ a.el ]
| (defcustom a-cus-var 'a-value
| "The documentation of `a-cus-var'.")
| (provide 'a)
`
and do:
(require 'a)
(unload-feature 'a)
Now a-cus-var is not bound, but when I do M-x customize
