From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: Bug in Custom apparently due to Custom Themes. Date: Sat, 13 May 2006 23:40:31 -0500 (CDT) Message-ID: <200605140440.k4E4eVkx007667@jane.dms.auburn.edu> References: <200605130245.k4D2jgOL004323@jane.dms.auburn.edu> <200605130313.k4D3DRLb004371@jane.dms.auburn.edu> <87r72xucas.fsf@stupidchicken.com> <200605140321.k4E3LgMq007569@jane.dms.auburn.edu> <87d5ehw9hr.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1147581719 18144 80.91.229.2 (14 May 2006 04:41:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 14 May 2006 04:41:59 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 14 06:41:58 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Ff8QW-0004ko-8D for ged-emacs-devel@m.gmane.org; Sun, 14 May 2006 06:41:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ff8QV-0002Nd-IJ for ged-emacs-devel@m.gmane.org; Sun, 14 May 2006 00:41:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ff8QH-0002NY-6e for emacs-devel@gnu.org; Sun, 14 May 2006 00:41:41 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ff8QE-0002K4-6n for emacs-devel@gnu.org; Sun, 14 May 2006 00:41:40 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ff8QE-0002K1-3Q for emacs-devel@gnu.org; Sun, 14 May 2006 00:41:38 -0400 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Ff8SL-0000xG-1M for emacs-devel@gnu.org; Sun, 14 May 2006 00:43:49 -0400 Original-Received: from jane.dms.auburn.edu (jane.dms.auburn.edu [131.204.53.201]) by manatee.dms.auburn.edu (8.13.6/8.13.6) with ESMTP id k4E4fbYY006708; Sat, 13 May 2006 23:41:37 -0500 (CDT) Original-Received: from jane.dms.auburn.edu (localhost [127.0.0.1]) by jane.dms.auburn.edu (8.13.4+Sun/8.13.4) with ESMTP id k4E4eW8C007670; Sat, 13 May 2006 23:40:32 -0500 (CDT) Original-Received: (from teirllm@localhost) by jane.dms.auburn.edu (8.13.4+Sun/8.13.3/Submit) id k4E4eVkx007667; Sat, 13 May 2006 23:40:31 -0500 (CDT) X-Authentication-Warning: jane.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: cyd@stupidchicken.com In-reply-to: <87d5ehw9hr.fsf@stupidchicken.com> (message from Chong Yidong on Sat, 13 May 2006 23:50:08 -0400) 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:54430 Archived-At: Chong Yidong wrote: > Start Emacs, assuming that fill-column is at its standard value of 70 > and do > > M-: (setq-default fill-column 71) > > `M-x customize-option fill-column RET' > > Edit to 72 and set for current session, using the State Menu. > > Then choose "Erase Customization" from the State Menu. > > The value should now be 70 and the State STANDARD. > > Instead, the value is 71 and we see: > > CHANGED outside Customize; operating on it here may be unreliable. I don't see the problem: the value 71 is the last value that fill-column had before it was changed with customize. That's why erasing customizations brings back this value. Do you use Custom at all? The problem is so obvious that I do not know what there is to explain. "Erase Customization" is supposed to restore the standard value (or themed value if there are themes) and _not_ the last _rogue_ value assigned to the variable, which may have been assigned ages ago, and changed twenty times through Custom since. That value is meaningless, which is why that `changed' theme is completely meaningless and should be eliminated. What I described above constitutes an incompatible change, which eliminates completely essential and well documented functionality (reverting to the default) and replaces it with nonsensical behavior. It is a serious bug. Sincerely, Luc.