From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: Why is custom--inhibit-theme-enable not t by default? Date: Tue, 12 Jun 2018 12:54:20 -0700 (PDT) Message-ID: References: <<10b7bd657091b074d8da1bf1ae35b1f4.squirrel@dancol.org> <83h8m8owp2.fsf@gnu.org> <48a7bd1277a18dd0a68d06cd8b022062.squirrel@dancol.org>> <<83vaao3qrn.fsf@gnu.org>> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1528833162 22923 195.159.176.226 (12 Jun 2018 19:52:42 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 12 Jun 2018 19:52:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii , dancol@dancol.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 12 21:52:37 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fSpLJ-0005qL-MW for ged-emacs-devel@m.gmane.org; Tue, 12 Jun 2018 21:52:37 +0200 Original-Received: from localhost ([::1]:58203 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSpNP-0001wd-5u for ged-emacs-devel@m.gmane.org; Tue, 12 Jun 2018 15:54:47 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44051) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fSpNH-0001wW-Ln for emacs-devel@gnu.org; Tue, 12 Jun 2018 15:54:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fSpNG-00074f-Ql for emacs-devel@gnu.org; Tue, 12 Jun 2018 15:54:39 -0400 Original-Received: from aserp2120.oracle.com ([141.146.126.78]:40904) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fSpNB-00071S-9f; Tue, 12 Jun 2018 15:54:33 -0400 Original-Received: from pps.filterd (aserp2120.oracle.com [127.0.0.1]) by aserp2120.oracle.com (8.16.0.22/8.16.0.22) with SMTP id w5CJouNN034531; Tue, 12 Jun 2018 19:54:22 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2017-10-26; bh=zHfZ04X6XPuBBek0pn1EgXVVc2VTx04EpsNNaiqYemk=; b=nuprQ4jjzG3St4b5+Cv3FnEZL2ms9MEt2hrrWau3p2a8nW6C2kLKkwp17esF6NdpvR1b 8zJFdSDGashCVeOfhIZhV5TqfZ0UOwPAObmflg12bqbM29sNPcbiirF0HJm+K3YT+oZb hQ++ygXtNicgdDKlOMvXbFyPL43MCwrugd7n60VSPK/HwLPMJUH+6m6fcqtk9t3bVC4u 2mU840EgxZNU206+QJc1/PtIAPFo1uTw4mOe5Khy8GcuKWuVTJ3ldosQaOIo3/cTNrYr qJ6Zx51NS3HS9vdiljlyAVPnKz/BfW7gscCjI0USMweuIIR8I1ppFXZAeOCEqBUemd7x SA== Original-Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by aserp2120.oracle.com with ESMTP id 2jgecxju58-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 12 Jun 2018 19:54:22 +0000 Original-Received: from aserv0121.oracle.com (aserv0121.oracle.com [141.146.126.235]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id w5CJsMt2010488 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 12 Jun 2018 19:54:22 GMT Original-Received: from abhmp0007.oracle.com (abhmp0007.oracle.com [141.146.116.13]) by aserv0121.oracle.com (8.14.4/8.13.8) with ESMTP id w5CJsLYT006735; Tue, 12 Jun 2018 19:54:21 GMT In-Reply-To: <<83vaao3qrn.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4690.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=8922 signatures=668702 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=810 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806120221 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 141.146.126.78 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:226273 Archived-At: > > > I think themes are special in this regard: loading a theme activates > > > it. > > > > Why did we do it that way? >=20 > History, I guess. AFAIR, it always has been that way. Maybe we did > it for compatibility with themes that were available outside of Emacs > before Emacs supported themes? No, not if you mean color themes (`color-theme.el'). Loading them does _not_ activate them. There are explicit functions for installing a color theme and invoking (activating) it. (And unlike the case for custom themes, you can undo the application of a color theme.) http://www.nongnu.org/color-theme/ http://download.savannah.nongnu.org/releases/color-theme/ > Or maybe because [custom] themes are just giant > series of variable settings? That's possible. Initially, custom themes were just variable settings, IIRC - there was no attempt to imitate color themes. Later, Chong Yidong added such imitation. > I really don't know. We have this commentary in custom.el: >=20 > ;; Each theme is stored in a theme file, with filename THEME-theme.el. > ;; Loading a theme basically involves calling (load "THEME-theme") > ;; This is done by the function `load-theme'. Loading a theme > ;; automatically enables it. >=20 > You will see that load-theme reads the file, then evaluates the > buffer, so 'load' will do the same. >=20 > > Is it too late to change it? Loading _anything_ shouldn't activate > > it. I don't see a need to carve out a special case for themes. Yes.