unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: Custom themes and precedence
Date: Sun, 02 Oct 2011 04:40:10 -0400	[thread overview]
Message-ID: <m21uuvu6qd.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <jwvipo81769.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 01 Oct 2011 22:04:30 -0400")


on Sat Oct 01 2011, Stefan Monnier <monnier-AT-iro.umontreal.ca> wrote:

>>>> I customized default-frame-alist in the theme for machine X... which
>
>>>> worked fine until I customized default-frame-alist "non-themedly"
>>>> somewhere else.  That caused the new setting to go into the "user" theme
>>>> *which takes precedence over all others*.  That last bit isn't working
>>>> out so well for my use-case.  Should this usage be accomodated, is it
>>>> outside the intended applications of themes, or...?
>>> Non-theme customization settings are intended to take precedence over
>>> theme settings.  The idea is that if you load a theme that's not written
>>> by you, it is easy to use Customize to override some of its settings.
>> I guess the question is, what about themes that *are* written by me,
>> that I may want to switch on or off programmatically?
>
> One approach is to encourage such users to put all their customizations
> into themes (i.e. avoid the "user" theme).

Heh.  Is that easier in Emacs24 than it is in 23?

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com



      reply	other threads:[~2011-10-02  8:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 23:59 Custom themes and precedence Dave Abrahams
2011-10-01 17:58 ` Chong Yidong
2011-10-01 18:27   ` Dave Abrahams
2011-10-02  2:04     ` Stefan Monnier
2011-10-02  8:40       ` Dave Abrahams [this message]

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=m21uuvu6qd.fsf@pluto.luannocracy.com \
    --to=dave@boostpro.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).