Re: Bad value to a defcustom makes choices unavailable

[Lennart Borgman]

Luc Teirlinck wrote:

> Lennart Borgman wrote:
>
>   Let us say that someone writes a defcustom in a package he distributes. 
>   Later she/he for some reason changes the list of choices. If a user has 
>   saved a value through custom that now no longer exists he can not 
>   correct it through custom.
>
> Actually, I would guess that Custom will not allow you to set it to an
> illegal value in your custom-set-variables form.  Did you actually try
> it?
>  
Of course I did not try...  ;-)

Sorry, no I did not try, but yes, custom-set-variables of course no 
nothing about the choices if the package is not loaded. And when I 
tested now I found that even in the case where the package is loaded 
custom will set the bad value.