unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, help-gnu-emacs@gnu.org
Subject: RE: RFC: Flavors - naming significant sets of customizations
Date: Mon, 25 Nov 2013 13:11:12 -0800 (PST)	[thread overview]
Message-ID: <0363e370-eb7a-4d41-a09d-f16f40499e7e@default> (raw)
In-Reply-To: <jwvk3fwqkck.fsf-monnier+gmane.emacs.help@gnu.org>

> > However, themes are not very 'hygienic' -- you cannot easily roll back a
> > whole theme; when you choose a new theme, it works on top of the already
> > chosen theme, with all the non-overridden settings still active.
> 
> Maybe I don't understand, but it sounds like a bug.

It is.  Bug ##15687:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15687

> Or maybe a mis-use: custom themes *can* be stacked, so if you want to
> replace a previous theme with a new one, then you need to remove the old
> and add the new one.  Maybe the UI needs some work to make it more clear
> (and make it easier to switch between themes).

The bug is not the fact that you can accumulate the effects of multiple
custom themes.  The bug is the fact that you cannot restore the state of
Emacs before any theme was applied.  There is no way to take a snapshot
of Emacs before theming and then restore to that.

You can add themes, for a cumulative effect, or you can replace the use
of one theme by another, but you cannot undo a theme, i.e., you cannot
untheme.

Such undoing was, and still is, trivial to accomplish with color themes:
http://www.nongnu.org/color-theme/.

This is the main reason that it is wrong to think of Emacs custom themes
as replacing color themes or, as is commonly stated, the former make the
latter obsolete.  So far, each has some advantages over the other.



  reply	other threads:[~2013-11-25 21:11 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 19:31 RFC: Flavors - naming significant sets of customizations ian.tegebo
2013-11-25 19:44 ` Jambunathan K
2013-11-25 19:54   ` Drew Adams
2013-11-25 20:04     ` Jambunathan K
2013-11-25 21:14       ` Drew Adams
2013-11-25 19:54 ` Stefan Monnier
2013-11-25 20:19   ` Dirk-Jan C. Binnema
2013-11-25 20:27     ` Jambunathan K
2013-11-25 20:50     ` Stefan Monnier
2013-11-25 21:11       ` Drew Adams [this message]
2013-11-26  2:12         ` William G. Gardella
2013-11-26  2:15           ` William G. Gardella
2013-11-26  2:25             ` William G. Gardella
     [not found]             ` <mailman.7131.1385432744.10748.help-gnu-emacs@gnu.org>
2013-11-26  3:12               ` Emanuel Berg
2013-11-26 14:35           ` Drew Adams
     [not found]       ` <mailman.7112.1385413891.10748.help-gnu-emacs@gnu.org>
2013-11-26  0:13         ` Stefan Monnier
2013-11-26  1:41           ` Drew Adams
2013-11-25 21:10     ` Drew Adams
2013-11-25 21:05 ` Peter Dyballa
2013-11-25 21:25 ` Jambunathan K
2013-11-26  1:03 ` Emanuel Berg
2013-11-26  9:42 ` Thien-Thi Nguyen
     [not found] ` <mailman.7101.1385409281.10748.help-gnu-emacs@gnu.org>
2013-11-25 20:04   ` ian.tegebo
2013-11-26 20:15   ` Ted Zlatanov
2013-11-26 20:33     ` Emanuel Berg
2013-11-26 21:00 ` Peter Dyballa
2013-11-27  1:22   ` Stefan Monnier
     [not found] ` <mailman.7149.1385458742.10748.help-gnu-emacs@gnu.org>
2013-11-27  4:03   ` Emanuel Berg
2013-11-29  1:40 ` Rustom Mody
2013-11-29  4:24   ` Emanuel Berg
2013-11-29  5:56     ` Rustom Mody
2013-11-30  1:05       ` Emanuel Berg
2013-11-30  5:52         ` Jambunathan K
2013-11-30  6:06           ` Jambunathan K
2013-11-30  6:56           ` Jambunathan K
     [not found]           ` <mailman.7606.1385794704.10748.help-gnu-emacs@gnu.org>
2013-11-30  7:49             ` Emanuel Berg
     [not found]         ` <mailman.7603.1385790839.10748.help-gnu-emacs@gnu.org>
2013-11-30  7:57           ` Emanuel Berg
2013-11-30 14:22         ` Emanuel Berg
2013-12-01  6:18           ` Jambunathan K
2013-12-01  6:30           ` Jambunathan K
     [not found]           ` <mailman.7689.1385878732.10748.help-gnu-emacs@gnu.org>
2013-12-01 16:27             ` Emanuel Berg
2013-12-02  5:21               ` Jambunathan K
2013-12-02 16:29                 ` Emanuel Berg
2013-12-02 17:07                   ` Emanuel Berg
2013-12-03 12:29                   ` Jambunathan K
     [not found]                   ` <mailman.7971.1386070312.10748.help-gnu-emacs@gnu.org>
2013-12-03 21:27                     ` Emanuel Berg
2013-12-04  7:25                       ` Jambunathan K
     [not found]                       ` <mailman.8057.1386141963.10748.help-gnu-emacs@gnu.org>
2013-12-04 17:50                         ` Emanuel Berg
     [not found]           ` <mailman.7691.1385879486.10748.help-gnu-emacs@gnu.org>
2013-12-01 16:29             ` Emanuel Berg
2013-11-29  8:31     ` Yuri Khan
2013-11-29 18:00     ` Jambunathan K
     [not found]     ` <mailman.7486.1385748092.10748.help-gnu-emacs@gnu.org>
2013-11-29 19:13       ` Emanuel Berg
2013-12-01  7:09         ` Jambunathan K
2013-12-01 20:57           ` Emanuel Berg
2013-12-02  5:25             ` Jambunathan K
2013-12-02  5:57               ` Jambunathan K
2013-12-02 16:47                 ` Emanuel Berg
2013-12-02 16:34               ` Emanuel Berg
     [not found]               ` <mailman.7875.1386002111.10748.help-gnu-emacs@gnu.org>
2013-12-02 22:23                 ` Emanuel Berg
2013-12-02  0:51           ` Emanuel Berg
     [not found]         ` <mailman.7693.1385881824.10748.help-gnu-emacs@gnu.org>
2013-12-01 16:35           ` Emanuel Berg
2013-12-01 20:40             ` Emanuel Berg
2013-11-29 19:55       ` Emanuel Berg
2013-11-30  2:52         ` Rustom Mody
2013-11-30  3:28           ` Emanuel Berg
     [not found]     ` <mailman.7436.1385713911.10748.help-gnu-emacs@gnu.org>
2013-12-04 17:52       ` Ted Zlatanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0363e370-eb7a-4d41-a09d-f16f40499e7e@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).