unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: torys.anderson@gmail.com (Tory S. Anderson)
To: Rasmus <rasmus@gmx.us>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Why do themes stack?
Date: Sat, 31 Jan 2015 08:37:40 -0500	[thread overview]
Message-ID: <87oapfnk9n.fsf@gmail.com> (raw)
In-Reply-To: <87sierrsxm.fsf@gmx.us> (rasmus@gmx.us's message of "Sat, 31 Jan 2015 14:16:53 +0100")

Thanks for the snippet; that's useful. 

I guess I have yet to imagine someone who wants to mix their paints manually, so to speak, rather than just putting them in a bottle (making a custom theme). 

Rasmus <rasmus@gmx.us> writes:

> torys.anderson@gmail.com (Tory S. Anderson) writes:
>
>> Why is it implemented this way? Does anyone out there actually gain
>> utility from theme stacking? Or am I doing something wrong? I would
>> think the simpler implementation would simply to have "load theme"
>> automatically disable the present theme, which is both conceptually
>> and pragmatically easier. But the manual doesn't seem to mention much
>> about themes, so I haven't found an explanation (or possible use) for
>> this stacking implementation.
>
> Some people use it for overlaying themes on top of the default theme,
> e.g. for different.
>
> You could just do something like this, I guess:
>
> (defun my/load-theme ()
>        "call load-theme, but disable all themes first"
>        (interactive)
>        (call-interactively 'load-theme)
>        (mapc 'disable-theme (cdr-safe custom-enabled-themes)))



  reply	other threads:[~2015-01-31 13:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-31 12:54 Why do themes stack? Tory S. Anderson
2015-01-31 13:16 ` Rasmus
2015-01-31 13:37   ` Tory S. Anderson [this message]
2015-01-31 13:56 ` Artur Malabarba
2015-01-31 14:32   ` Tory S. Anderson

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=87oapfnk9n.fsf@gmail.com \
    --to=torys.anderson@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rasmus@gmx.us \
    /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).