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: Starnge comment in Custom Theme code. Date: Sun, 25 Dec 2005 22:21:57 -0600 (CST) Message-ID: <200512260421.jBQ4Lvp00108@raven.dms.auburn.edu> 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> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1135571059 26587 80.91.229.2 (26 Dec 2005 04:24:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 26 Dec 2005 04:24:19 +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 05:24:17 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 1EqjuB-0005uB-60 for ged-emacs-devel@m.gmane.org; Mon, 26 Dec 2005 05:24:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EqjvM-00075B-CB for ged-emacs-devel@m.gmane.org; Sun, 25 Dec 2005 23:25:28 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EqjvC-000756-UK for emacs-devel@gnu.org; Sun, 25 Dec 2005 23:25:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EqjvB-00074t-EK for emacs-devel@gnu.org; Sun, 25 Dec 2005 23:25:18 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EqjvB-00074q-Bb for emacs-devel@gnu.org; Sun, 25 Dec 2005 23:25:17 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Eqjuv-0006rF-LS; Sun, 25 Dec 2005 23:25:01 -0500 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.13.3+Sun/8.13.3) with ESMTP id jBQ4O1ix017764; Sun, 25 Dec 2005 22:24:02 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id jBQ4Lvp00108; Sun, 25 Dec 2005 22:21:57 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: rms@gnu.org In-reply-to: (rms@gnu.org) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.1 (manatee.dms.auburn.edu [131.204.53.104]); Sun, 25 Dec 2005 22:24:02 -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:48371 Archived-At: Richard Stallman wrote: 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. I believe that setq expresses just as much an individual preference by the user than a saving or setting through Custom. If a program did the setq, the situation may be worse, because the program may be relying on the setq-ed value for its proper functioning. One example of a problem that can occur if loading a theme overrides "rogue" values, but not the user theme: If the user sets cua-mode via Custom then cua-mode seems to set transient-mark-mode, delete-selection-mode and pc-selection-mode using setq or minor mode invocation. Now the user loads a theme with tons of settings, one of them setting one of these to some other value. Even if the theme also sets cua-mode to nil, cua-mode stays enabled, because the theme does not override the cua Custom setting. With the cua-set variables away from their cua-defaults, cua-mode is, I believe, pretty much going to become disfunctional to the user. There are also, I believe, going to be problems when the user, seeing the inconsistency, disables cua-mode. Then cua-mode seems to reestablish its own saved old user settings, overriding the theme again. Sincerely, Luc.