From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: Bug, probably related to Custom Themes. Date: Sat, 24 Dec 2005 11:33:16 -0500 Message-ID: References: <200512210254.jBL2sj814876@raven.dms.auburn.edu> <87mziuqp2x.fsf@stupidchicken.com> <200512211840.jBLIefx25655@raven.dms.auburn.edu> <87vexiw3w4.fsf@stupidchicken.com> <200512212258.jBLMwt329838@raven.dms.auburn.edu> <200512230426.jBN4QQD18470@raven.dms.auburn.edu> <200512232318.jBNNIpH29992@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1135442694 17696 80.91.229.2 (24 Dec 2005 16:44:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 24 Dec 2005 16:44:54 +0000 (UTC) Cc: cyd@stupidchicken.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 24 17:44:53 2005 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 1EqCVn-0001Jb-MJ for ged-emacs-devel@m.gmane.org; Sat, 24 Dec 2005 17:44:51 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EqCWu-00086h-DQ for ged-emacs-devel@m.gmane.org; Sat, 24 Dec 2005 11:46:00 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EqCM3-0004CY-Ju for emacs-devel@gnu.org; Sat, 24 Dec 2005 11:34:48 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EqCM1-0004Bl-Mk for emacs-devel@gnu.org; Sat, 24 Dec 2005 11:34:46 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EqCLz-0004BZ-Qp for emacs-devel@gnu.org; Sat, 24 Dec 2005 11:34:44 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EqCLU-0005iK-Me for emacs-devel@gnu.org; Sat, 24 Dec 2005 11:34:12 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1EqCKa-0004YL-0t; Sat, 24 Dec 2005 11:33:16 -0500 Original-To: Luc Teirlinck In-reply-to: <200512232318.jBNNIpH29992@raven.dms.auburn.edu> (message from Luc Teirlinck on Fri, 23 Dec 2005 17:18:51 -0600 (CST)) 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:48310 Archived-At: That treats a symptom instead of the _real_ underlying bug. I have already given one more example of a "surface bug" that is caused by the same underlying bug: if a setting is set by a theme, the "Erase Customization" item of the State Menu is enabled, whereas it should not be, because it is not going to have any effect (which is confusing to the user, because the State message says and keeps saying: "SAVED and set"). That seems right. I see that Yidong just added a feature to make it display as "THEMED" instead. Does that fix this problem? What happens is that, since I just set column-number-mode to its standard-value, Custom thought that it just had to erase a line in my custom-set-variables form (that was not there). Instead, Custom should have written a line in my custom-set-variables form explicitly setting column-number-mode to nil, to override my theme. Indeed, that is a bug. That part of Custom needs to check for theme values. Obviously whenever Custom checks the value of standard-value, a bug is likely to result. Yes, it seems like we need to check all of those places and make sure they take account of themes. Yidong, could you please do that? Or was this done by the patch you recently installed?