Re: unload-feature and defcustom.

[David Kastrup]

Lute Kamstra <address@hidden> 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-feature 'a)
>
> I think this is undesirable.  Could this be easily fixed?  (Maybe by
> letting customize ignore unbound vars.)  Or is better to put this on
> the post-release todo list?

post-release, I'd say.  It should be noted that files generated with
update-file-autoloads and its cousins actually only contain defvar,
not defcustom, but maybe those are not the most important ones to
unload in general.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum