From: Eric S Fraga <firstname.lastname@example.org>
Subject: Re: Marking thread as read
Date: Fri, 30 Jun 2023 10:16:12 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On Friday, 30 Jun 2023 at 04:28, Michael Heerdegen wrote:
> After reading the Gnus manual a bit I take "killed" as a subset of
> "read". k for example behaves, and is documented, similarly.
> Internally `gnus-summary-mark-article-as-read' is used, just marking is
> done with `gnus-killed-mark' - probably to indicate that you have not
> handled the articles by hand.
This makes sense but has some side effects, IIUC. In particular,
adaptive scoring may be affected?
But I see that Adam has posted some code so all is good. :-)
Eric S Fraga via gnus (Emacs 30.0.50 2023-06-19) on Debian 12.0
next prev parent reply other threads:[~2023-06-30 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 4:02 Alshehhi Family
2023-06-29 13:07 ` Eric S Fraga
2023-06-29 13:26 ` Eric S Fraga
2023-06-30 2:28 ` Michael Heerdegen
2023-06-30 9:16 ` Eric S Fraga [this message]
2023-06-29 16:33 ` Adam Sjøgren
2023-07-01 15:23 Alshehhi Family
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).