|
From: | Lennart Borgman |
Subject: | Re: Bad value to a defcustom makes choices unavailable |
Date: | Mon, 01 Aug 2005 20:29:32 +0200 |
User-agent: | Mozilla Thunderbird 1.0.6 (Windows/20050716) |
Luc Teirlinck 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. Perhaps the user does not know elisp at all.Lennart Borgman wrote:Maybe I am misunderstanding you, but in my case I want another value than the available choices to be an error. I want the user to be able to correct this by choosing one of the available alternatives (ie if they were available).The illegal value could only have been obtained by the user setting it outside Custom, for instance with a setq in his .emacs. The user can not reliably correct the problem through Custom, he has to correct the problem where the problem originated (probably .emacs).
I think it would be good then if the list of choices were available.
[Prev in Thread] | Current Thread | [Next in Thread] |