From: Scott A Crosby <scrosby@cs.rice.edu>
Subject: gnus-summary-hilight change
Date: 01 Aug 2002 17:09:48 -0500 [thread overview]
Message-ID: <oydbs8mdydv.fsf@sam.cs.rice.edu> (raw)
I was looking at gnus-summary-hilight with scoring and thought that we
should have a high&low level. IE, anything between high&low should be
colored normal, not just messages with a score of normal.
Implementation:
(setq my-gnus-high-level 100)
(setq my-gnus-low-level -500)
(setq gnus-summary-highlight
'(((= mark gnus-canceled-mark)
. gnus-summary-cancelled-face)
((and (> score my-gnus-high-level)
(or (= mark gnus-dormant-mark)
(= mark gnus-ticked-mark)))
. gnus-summary-high-ticked-face)
((and (< score my-gnus-low-level)
(or (= mark gnus-dormant-mark)
(= mark gnus-ticked-mark)))
. gnus-summary-low-ticked-face)
((or (= mark gnus-dormant-mark)
(= mark gnus-ticked-mark))
. gnus-summary-normal-ticked-face)
((and (> score my-gnus-high-level) (= mark gnus-ancient-mark))
. gnus-summary-high-ancient-face)
((and (< score my-gnus-low-level) (= mark gnus-ancient-mark))
. gnus-summary-low-ancient-face)
((= mark gnus-ancient-mark)
. gnus-summary-normal-ancient-face)
((and (> score my-gnus-high-level) (= mark gnus-unread-mark))
. gnus-summary-high-unread-face)
((and (< score my-gnus-low-level) (= mark gnus-unread-mark))
. gnus-summary-low-unread-face)
((= mark gnus-unread-mark)
. gnus-summary-normal-unread-face)
((and (> score my-gnus-high-level) (memq mark (list gnus-downloadable-mark
gnus-undownloaded-mark)))
. gnus-summary-high-unread-face)
((and (< score my-gnus-low-level) (memq mark (list gnus-downloadable-mark
gnus-undownloaded-mark)))
. gnus-summary-low-unread-face)
((memq mark (list gnus-downloadable-mark gnus-undownloaded-mark))
. gnus-summary-normal-unread-face)
((> score my-gnus-high-level)
. gnus-summary-high-read-face)
((< score my-gnus-low-level)
. gnus-summary-low-read-face)
(t
. gnus-summary-normal-read-face)))
Scott
reply other threads:[~2002-08-01 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=oydbs8mdydv.fsf@sam.cs.rice.edu \
--to=scrosby@cs.rice.edu \
/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).