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: Starnge comment in Custom Theme code. Date: Sun, 25 Dec 2005 21:20:24 -0500 Message-ID: References: <200512241630.jBOGU6H09878@raven.dms.auburn.edu> <87bqz6h0lw.fsf@stupidchicken.com> <200512241802.jBOI2qd11015@raven.dms.auburn.edu> <87ek428hrt.fsf@stupidchicken.com> <200512250232.jBP2WDO16031@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 1135563787 13463 80.91.229.2 (26 Dec 2005 02:23:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 26 Dec 2005 02:23:07 +0000 (UTC) Cc: cyd@stupidchicken.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 26 03:23:06 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 1Eqi0u-0000mw-TN for ged-emacs-devel@m.gmane.org; Mon, 26 Dec 2005 03:23:05 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eqi26-0000ja-2I for ged-emacs-devel@m.gmane.org; Sun, 25 Dec 2005 21:24:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Eqhzz-0007mV-L6 for emacs-devel@gnu.org; Sun, 25 Dec 2005 21:22:08 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Eqhzy-0007li-KV for emacs-devel@gnu.org; Sun, 25 Dec 2005 21:22:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Eqhzy-0007lQ-79 for emacs-devel@gnu.org; Sun, 25 Dec 2005 21:22:06 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Eqhzi-00006i-EE for emacs-devel@gnu.org; Sun, 25 Dec 2005 21:21:50 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1EqhyK-0001Cw-OE; Sun, 25 Dec 2005 21:20:24 -0500 Original-To: Luc Teirlinck In-reply-to: <200512250232.jBP2WDO16031@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 24 Dec 2005 20:32:13 -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:48368 Archived-At: I referred to the following, which Richard wrote when we discussed Custom Themes many months ago: As for settings with setq, those should make the variable a rogue, as now. When the variable is a rogue, theme operations should not touch it. Yes, I did say that in a message. However, what I subsequently implemented seems more flexible than that, because it allows themes to set these variables. If there are some bugs in custom theme handling of them, I'd rather fix the bugs than make custom themes not work on them. But what _really_ matters is that we decided a few days ago to consider Custom Themes (except for the user theme) as alternative "standard" values. What Yidong did (and I think it was right) is call them "themed" values. Themed values and standard values are equivalent _in regard to user Custom settings_, but that's only because both theme values and default values both come "after" user Custom settings. It does not mean they are equivalent in other ways. I am not sure what is the right way to deal with theme settings of variables that have been setq's outside Custom, but the argument you made this time does not seem persuasive.