From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: coloring process-marked articles
Date: Fri, 28 Sep 2001 14:16:45 +1000 [thread overview]
Message-ID: <87d74chrv6.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <m366a47yg5.fsf@wolfram.com> ("Bill White"'s message of "Thu, 27 Sep 2001 23:04:42 -0500")
On Thu, 27 Sep 2001, Bill White wrote:
> I was thinking today that it would be nice to colorize process-marked
> articles in the summary buffer. Here's a way to do it by customizing
> gnus-summary-highlight, but this way I'll miss the nifty things that
> are occasionally added to gnus-summary-highlight. Is there a better
> way to do it?
>
> ,----[ ~/.gnus ]
> | (defface gnus-summary-process-face
> | '((((class color))
> | (:foreground "deeppink" :background "black")))
> | "Face used for process-marked articles.")
> `----
>
> ,----[ C-h v gnus-summary-highlight RET ]
> | gnus-summary-highlight's value is shown below.
> |
> | [...]
> |
> | Value:
> | (((= mark gnus-canceled-mark)
> | . gnus-summary-cancelled-face)
> => | ((memq
> => | (gnus-summary-article-number)
> => | gnus-newsgroup-processable)
> => | . gnus-summary-process-face)
> |
> | [...]
> |
> `----
Presumably you set this by putting a complete copy of
`gnus-summary-highlight' in your .gnus, right? Otherwise you wouldn't be
asking.
So, it's basically an alist of values; try:
(require 'gnus-sum)
(require 'cl)
(pushnew '((memq (gnus-summary-article-number)
gnus-newsgroup-processable)
. gnus-summary-process-face)
gnus-summary-highlight
:test equal)
That should do what you want and be safe from multiple evaluations.
Daniel
--
It is always possible to aglutenate multiple separate problems into a single
complex interdependent solution. In most cases this is a bad idea.
-- RFC 1925
next prev parent reply other threads:[~2001-09-28 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 4:04 Bill White
2001-09-28 4:16 ` Daniel Pittman [this message]
2001-09-28 5:06 ` Bill White
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=87d74chrv6.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).