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: Custom themes Date: Tue, 28 Jun 2005 23:28:25 -0500 (CDT) Message-ID: <200506290428.j5T4SPp25779@raven.dms.auburn.edu> References: <200506250127.j5P1RWJ11778@raven.dms.auburn.edu> <871x6nytam.fsf-monnier+emacs@gnu.org> <200506281441.j5SEfba23972@raven.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1120019650 15951 80.91.229.2 (29 Jun 2005 04:34:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2005 04:34:10 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 06:33:57 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DnUFu-0007Tw-5r for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2005 06:32:59 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DnUNs-00032q-Lq for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2005 00:41:12 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DnULe-0002eP-Kc for emacs-devel@gnu.org; Wed, 29 Jun 2005 00:38:55 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DnULT-0002Xs-Jl for emacs-devel@gnu.org; Wed, 29 Jun 2005 00:38:44 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DnULR-0002Up-Vs for emacs-devel@gnu.org; Wed, 29 Jun 2005 00:38:42 -0400 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DnUHo-00026q-2W; Wed, 29 Jun 2005 00:34:56 -0400 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id j5T4UBCK023532; Tue, 28 Jun 2005 23:30:12 -0500 (CDT) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j5T4SPp25779; Tue, 28 Jun 2005 23:28:25 -0500 (CDT) 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-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:39867 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:39867 Richard Stallman wrote: That sounds like a good approach. I see a few approaches that could make sense: 1. Most recent takes priority. 2. Let user specify the priority order. 3. Don't allow loading themes that conflict. 4. Ask the user what to do, each time there is a conflict. It would appear that "unrequiring" of individual themes does not currently work after all, as I already pointed out. In that case, just allowing to require or load implements (1): Most recent wins. I do not understand "unconditional loading". Could you explain what you mean by that? `require-theme' checks whether the theme already has been loaded, by checking whether it is a member of `features'. In other words, it works just like a regular require. If it is already in features, `require-theme' does nothing. By "unconditional loading", I mean just loading the file without checking anything. My latest patches just mention both possibilities and let the user decide. I believe that a really natural and intuitive implementation of unrequiring individual themes (in fact just implementing _any_ unrequiring of individual themes) requires a lot more work. The current Custom Themes code does not appear to come close to succeeding in implementing _any_ form of individual unrequiring. My original impression that it did was erroneous. I doubt that the current Custom themes code even can be used as a _basis_ for that. Sincerely, Luc.