From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: "Daniel Colascione" Newsgroups: gmane.emacs.devel Subject: Re: Disabling custom themes Date: Wed, 13 Jun 2018 10:30:59 -0700 Message-ID: <14a50e1d1d2d1965df4ed4e438c3070a.squirrel@dancol.org> References: <10b7bd657091b074d8da1bf1ae35b1f4.squirrel@dancol.org> <83h8m8owp2.fsf@gnu.org> <48a7bd1277a18dd0a68d06cd8b022062.squirrel@dancol.org>> <83vaao3qrn.fsf@gnu.org>> <874li63iit.fsf@tcd.ie> <87602m1v94.fsf_-_@tcd.ie> <874li6iov3.fsf@ericabrahamsen.net> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1528911048 7780 195.159.176.226 (13 Jun 2018 17:30:48 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 13 Jun 2018 17:30:48 +0000 (UTC) User-Agent: SquirrelMail/1.4.23 [SVN] Cc: emacs-devel@gnu.org To: "Eric Abrahamsen" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 13 19:30:44 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 1fT9bW-0001uk-SU for ged-emacs-devel@m.gmane.org; Wed, 13 Jun 2018 19:30:43 +0200 Original-Received: from localhost ([::1]:35880 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fT9de-0005ye-0A for ged-emacs-devel@m.gmane.org; Wed, 13 Jun 2018 13:32:54 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49261) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fT9bp-0005Zn-Lx for emacs-devel@gnu.org; Wed, 13 Jun 2018 13:31:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fT9bo-0005sV-Lx for emacs-devel@gnu.org; Wed, 13 Jun 2018 13:31:01 -0400 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:42092) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fT9bo-0005o7-Dg for emacs-devel@gnu.org; Wed, 13 Jun 2018 13:31:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From:Subject:Date:References:In-Reply-To:Message-ID; bh=FmG9CNtwYqmbC2mEGtVvb40F7RcGrGptl1ztiDXuWfw=; b=Puxbyz3sbUJI0CfpydeN7E+IPQQ2r2KsoKG9UxDx7MMAxrlwoDYlcO64QhLg+Bh2+1uyDq3gn40bwixSu5Km3c2zbBNV3dWRJ5UmceyCllyxVrInWHbhx2+2UQR1Z5NMvmCx5fxdQv5uR+fKdDWis/aLn7Nn5OtqnblKSwNUu7mQW9FBnlrjcjUTkRFmFb1EgBCdXvNFzR5bjZOXOJPIqvvehYMdCbbSzzwmN6yl9RtPM1iJJRJEwFT6Vh0RBqEtztrbkGE4dycI1BhaWmHStg5PrUsZLG7ktfRx7XgELHkveBhCEZyZk+JYnHDYz4gK2Vc2MTGZkSS0nXen4U8wmQ==; Original-Received: from localhost ([127.0.0.1] helo=dancol.org) by dancol.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fT9bn-0002A0-3i; Wed, 13 Jun 2018 10:30:59 -0700 Original-Received: from 127.0.0.1 (SquirrelMail authenticated user dancol) by dancol.org with HTTP; Wed, 13 Jun 2018 10:30:59 -0700 In-Reply-To: <874li6iov3.fsf@ericabrahamsen.net> X-Priority: 3 (Normal) Importance: Normal X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:226299 Archived-At: > Drew Adams writes: > >>> Sorry, I'm not sure I completely understand what you mean (for example >>> w.r.t. "initial state" and "settings of the 'disabled' custom theme"), >>> but I've posted a recipe with what I think you're getting at to >>> bug#15687, where I think any further discussion of the effects of theme >>> disabling can be continued. >>> >>> Either way, thanks for the explanation and background. >> >> Thanks for reopening bug #15687. And from your post there >> I think you have understood. >> >> To try to clarify - >> >> I mean only that custom-theme enabling/disabling knows only >> about (custom) themes. It does not know about other user >> customizations, so it cannot restore them when it is disabled. >> >> What's missing is a function that captures the state of Emacs >> (anything that a custom state might modify) before any custom >> theme is applied, so that that state can be restored. >> >> Then you could (as you can with color themes) invoke that >> function to take a snapshot of your Emacs before "theming", >> and you could use that snapshot to restore your Emacs pretty >> much as it was before "theming". > > I would find this useful as well. I switch to `color-theme-dark-laptop' > at night (which is very nice), and would like to be able to switch back > to my own customized state the next morning. Wouldn't it be nice if we'd modeled visual styles on CSS? Applying a theme would just be enabling a stylesheet. The CSS model got things fundamentally right in a lot of ways that I think every other theme solution only approached.