Re: Bad value to a defcustom makes choices unavailable

[Per Abrahamsen <abraham@dina.kvl.dk>]

Lennart Borgman <lennart.borgman.073@student.lu.se> writes:

> 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.

He can, unless that functionality has been changed.  Customize will
present the invalid value in an sexp widget.  Which seems the most
reasonable thing to in the general case.

If he don't know what to do with an sexp, he can do a "Reset to
standard value", and then use the structured editor.

> I think it would be good then if the list of choices were available.

You could special case the "choice" widget (most widget can have
"invalid value", so the problem is general).  But I don't think the
code complexity would outweigh the minor convenience of not having to
do a "Reset to standard" first.