From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: feature request: differentiate between read and automatically marked read
Date: Thu, 03 Feb 2022 08:50:13 +0000 [thread overview]
Message-ID: <87pmo41ghm.fsf@ucl.ac.uk> (raw)
Hello all,
a simple feature request follows.
I use adaptive scoring and rely on it. It would be nice to be able to
distinguish between articles that I have read and those that have
automatically been marked as read because of their low score. At
present, any article with a negative score (but above the automatically
read threshold) that has been read and articles marked as read
automatically all use the 'gnus-summary-low-read' face. It would be
great to have a further level face, maybe 'gnus-summary-marked-read',
one for those beyond the threshold.
I must admit to not having looked at the code to see how easy this would
be to do. I will try to do so but thought I'd bring up the suggestion
first... ;-)
Thank you,
eric
--
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2
next reply other threads:[~2022-02-03 8:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:50 Eric S Fraga [this message]
2022-02-03 9:10 ` Eric S Fraga
2022-02-03 12:26 ` dick
2022-02-03 12:38 ` Tassilo Horn
2022-02-03 13:04 ` dick
2022-02-03 13:34 ` Eric S Fraga
2022-02-03 12:50 ` Eric S Fraga
2022-02-05 8:51 ` Uwe Brauer
2022-02-05 9:29 ` Eric S Fraga
2022-02-05 10:36 ` Uwe Brauer
2022-02-07 12:28 ` Eric S Fraga
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=87pmo41ghm.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).