From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Per Abrahamsen Newsgroups: gmane.emacs.devel Subject: Re: Bad value to a defcustom makes choices unavailable Date: Tue, 02 Aug 2005 18:09:57 +0200 Organization: The Church of Emacs Message-ID: References: <42EE43B6.2090409@student.lu.se> <200508011741.j71HflT04394@raven.dms.auburn.edu> <42EE60DA.6020701@student.lu.se> <200508011758.j71HwZS04956@raven.dms.auburn.edu> <42EE665A.3060208@student.lu.se> <200508011820.j71IKNr05302@raven.dms.auburn.edu> <42EE6A0C.7050807@student.lu.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1123000742 607 80.91.229.2 (2 Aug 2005 16:39:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 2 Aug 2005 16:39:02 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 02 18:38:59 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DzziG-0003HN-S0 for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2005 18:33:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dzzkx-0006eZ-RP for ged-emacs-devel@m.gmane.org; Tue, 02 Aug 2005 12:36:43 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dzzhn-0005d8-Oy for emacs-devel@gnu.org; Tue, 02 Aug 2005 12:33:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dzzhf-0005ZH-UR for emacs-devel@gnu.org; Tue, 02 Aug 2005 12:33:25 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dzzhe-0005ME-Hj for emacs-devel@gnu.org; Tue, 02 Aug 2005 12:33:18 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1Dzzbj-0001FH-Nf for emacs-devel@gnu.org; Tue, 02 Aug 2005 12:27:11 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DzzN6-0006jI-2a for emacs-devel@gnu.org; Tue, 02 Aug 2005 18:12:04 +0200 Original-Received: from sheridan.dina.kvl.dk ([130.225.40.227]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Aug 2005 18:12:04 +0200 Original-Received: from abraham by sheridan.dina.kvl.dk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 Aug 2005 18:12:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-To: emacs-devel@gnu.org Original-Lines: 20 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: sheridan.dina.kvl.dk X-Face: +kRV2]2q}lixHkE{U)mY#+6]{AH=yN~S9@IFiOa@X6?GM|8MBp/ Mail-Copies-To: nobody User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux) Cancel-Lock: sha1:BcvgV8OmuWox8N0vVRXzNM1o1sY= X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:41430 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:41430 Lennart Borgman 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.