unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Joost Kremers <joost.m.kremers@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: custom-themes BAD?
Date: Tue, 25 Feb 2014 09:45:20 -0800 (PST)	[thread overview]
Message-ID: <0eff6f35-c932-4857-9944-55850f832f36@default> (raw)
In-Reply-To: <<slrnlgpkad.3j2.joost.m.kremers@j.kremers4.news.arnhem.chello.nl>>

> > All the packages should be using font-lock-* faces as far as
> > possible.  Then the themes can all set the same set of faces
> > much more easily.
> 
> Better yet, packages should define their own faces but use the :inherit
> property to derive them from Emacs' standard faces. That way, users can
> customize faces in some mode/package and use the default ones in others,
> if they prefer.

Exactly.  And it's not just "better *yet*", as if the first
suggestion itself represented some improvement but not the
best improvement.  The first approach is generally misguided, IMO.

It is simply not the case that "all packages should be using
font-lock-* faces as far as possible."  That is bad advice, IMO.
Package designers should use their heads, keeping the package users
foremost in mind.

I also wonder about this part:

> > Then the themes can all set the same set of faces much more
> > easily.

Why should I care how easy it is for "themes to set" the same
set of faces?  What I care about is how easy it is for users
to customize a set of faces.  And for users of themes to control
them.

Now if it is the case that custom themes are "BAD", in that there
is no easy way to customize a set of faces across multiple
themes, then that would be something missing in the design of
custom themes.  That would not surprise me, but I'm no expert on
custom themes.



       reply	other threads:[~2014-02-25 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<ic1tyrdsrh.fsf@home.home>
     [not found] ` <<slrnlgpkad.3j2.joost.m.kremers@j.kremers4.news.arnhem.chello.nl>
2014-02-25 17:45   ` Drew Adams [this message]
2014-02-25 17:08 custom-themes BAD? Dan Espen
2014-02-25 17:22 ` Joost Kremers
2014-02-25 17:38   ` E Sabof
2014-02-25 17:54   ` Dan Espen
     [not found]   ` <mailman.16024.1393350344.10748.help-gnu-emacs@gnu.org>
2014-02-25 18:06     ` Dan Espen
2014-02-25 17:35 ` Drew Adams
     [not found] ` <mailman.16021.1393349758.10748.help-gnu-emacs@gnu.org>
2014-02-25 18:03   ` Dan Espen
2014-02-25 19:33     ` Rainer M Krug
     [not found]     ` <mailman.16038.1393356841.10748.help-gnu-emacs@gnu.org>
2014-02-25 19:48       ` Dan Espen
2014-02-25 20:04         ` Rainer M Krug
2014-02-25 21:05           ` W. Greenhouse
2014-02-25 22:19             ` Drew Adams

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=0eff6f35-c932-4857-9944-55850f832f36@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joost.m.kremers@gmail.com \
    /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).