From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: feature request: differentiate between read and automatically marked read
Date: Mon, 07 Feb 2022 12:28:38 +0000 [thread overview]
Message-ID: <87h79azwqx.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87r18hk3b4.fsf@mat.ucm.es>
On Saturday, 5 Feb 2022 at 11:36, Uwe Brauer wrote:
> Your messages are then in bold face (did you fiddle the setting of the
> display variable you mentioned earlier?)
Gnus has faces for the various levels of scores: high, normal, low; and
categories within these scores: ancient, read, ticked, and unread. And
then settings for what is a high or low scoring article:
gnus-summary-default-low-score, etc.
And, yes: I had to play with gnus-summary-highlight and added the
condition:
((< score gnus-summary-mark-below)
. gnus-summary-cancelled)
near the end of the list of conditions to use the gnus-summary-cancelled
face.
> BTW I wish that scoring would it a bit easier to set up, what you sent
Well, I guess I find it rather easy as it's either I for increase or L
for lower and then just follow the prompts with "?" available at each
prompt to remind you what the options are. There are also the V keymap
bindings in summary mode for seeing the effect of scores.
Adaptive scoring is trickier, mind you.
--
Eric S Fraga with org 9.5.2 in Emacs 29.0.50 on Debian 11.2
prev parent reply other threads:[~2022-02-07 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:50 Eric S Fraga
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 [this message]
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=87h79azwqx.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).