Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: ding@gnus.org
Subject: Re: Gnus faces
Date: Tue, 11 Jan 2011 19:58:41 +0100	[thread overview]
Message-ID: <877heb8dy6.fsf@member.fsf.org> (raw)
In-Reply-To: <874o9f5qxo.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 11 Jan 2011 11:46:27 -0500")

Chong Yidong <cyd@stupidchicken.com> writes:

> Gnus defines a large number of faces for the Group, Summary, and
> Article buffers.  This makes it a pain for those who want impose a
> uniform color scheme on their Emacs, who must chage every one of these
> faces.

True.

> It would be better for the Gnus faces to :inherit from the standard
> Emacs font-lock faces.  After all, font-lock highlighting is not used
> in Gnus.  Thoughts?

Yes, that wouldn't be a bad idea.  Additionally, Gnus has different
faces for e.g. groups with respect to the backend (mail or news), the
level (1-4), and the "emptyness" (has unread or ticked articles or not),
so there are 16 different faces

  gnus-group-{mail,news}-{1,2,3,4}{,-empty}

just for customizing the face of groups in the *Group* buffer.  The
problem is that those faces don't inherit from each other.  So if I'd
like to make all non-empty groups underlined, I have at least to modify
8 faces.

IMHO, I'd have an inheritance hierarchy with a top-level "abstract"
(i.e., not really used face) gnus-group, that is specialized by
emptyness, then backend, and finally by levels.  (I think that in times
of fast internet connections, the levels are the least important thing.
I'd even go that far and remove their different defaults.  Feel free to
disagree.)

Bye,
Tassilo
-- 
Sent from my Emacs



  parent reply	other threads:[~2011-01-11 18:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-11 16:46 Chong Yidong
2011-01-11 18:45 ` Lars Magne Ingebrigtsen
2011-01-11 18:58 ` Tassilo Horn [this message]
2011-01-11 22:56   ` James Cloos
2011-01-12  9:16     ` Štěpán Němec
2011-01-11 23:31   ` Andreas Schwab
2011-01-12  7:30     ` Tassilo Horn
2011-01-12  8:51       ` Andreas Schwab
2011-01-12  9:20         ` Tassilo Horn
2011-01-12  9:28           ` Andreas Schwab
2011-01-12 11:12             ` Tassilo Horn
2011-01-12 12:51               ` Andreas Schwab
2011-01-12 14:41                 ` Tassilo Horn
2011-01-12 14:51                   ` Andreas Schwab
2011-01-12 15:13                   ` Philipp Haselwarter
2011-01-12 16:30                     ` Tassilo Horn
2011-01-12  9:25         ` Philipp Haselwarter
2011-01-19 21:43 ` Ted Zlatanov
2011-01-11 17:40 gnus faces Robert D. Crawford

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

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

  git send-email \
    --in-reply-to=877heb8dy6.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=cyd@stupidchicken.com \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).