From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: ding@gnus.org
Subject: Re: Common "base" face for gnus-group-* and gnus-summary-*?
Date: Sat, 06 Feb 2016 16:27:25 +1100 [thread overview]
Message-ID: <8737t6s91e.fsf@gnus.org> (raw)
In-Reply-To: <m237tcdplh.fsf@boostpro.com> (Dave Abrahams's message of "Mon, 01 Feb 2016 14:37:30 -0800")
Dave Abrahams <dave@boostpro.com> writes:
> Seems to me that, in order to tune the way your gnus looks, it takes an
> inordinate amount of fiddling with faces because they have no common
> bases. Would it make sense to, e.g. make all the gnus-summary-* faces
> inherit a "gnus-summary" face, and maybe make all "gnus-summary-low-*"
> faces inherit a "gnus-summary-low" face, etc.
Yeah, I think that sounds like a good idea. Patches welcome.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-06 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 22:37 Dave Abrahams
2016-02-06 5:27 ` Lars Ingebrigtsen [this message]
2016-02-07 15:55 ` Dave Abrahams
2016-02-07 16:32 ` Adam Sjøgren
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=8737t6s91e.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=dave@boostpro.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).