From: Christopher Howard <christopher@librehacker.com>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: 75329@debbugs.gnu.org
Subject: bug#75329: 30.0.93; gnus: lowering thread score doesn't work on e-mail threads (...?)
Date: Thu, 09 Jan 2025 07:18:15 -0900 [thread overview]
Message-ID: <87sepshsfs.fsf@librehacker.com> (raw)
In-Reply-To: <154862.1736392991@alto.camomileplus.org> (Mike Kupfer's message of "Wed, 08 Jan 2025 19:23:11 -0800")
Mike Kupfer <kupfer@rawbw.com> writes:
> 1. select the email that started the thread, not just one near the top.
> (This might be an artifact of the thread that I tested on. You probably
> just need to select an email that everything afterwards refers to in the
> References header.)
>
> 2. Use "L t s t" (s, not e). I expect substring to be safe, because
> AFAIK, the message ID for one email cannot be a substring of the message
> ID for a second email, due to the angle brackets (<, >) being reserved.
Okay, thank you for the information. This is working for me as well, the way you described.
One issue for me here is how to get to the start of the thread quickly, since the actual start of the thread might be hidden. I suppose I could run (gnus-summary-insert-old-articles t) and then (gnus-summary-top-thread). But I know that gnus-summary-insert-old-articles can take a really long time in an IMAP summary buffer so I'm not sure if that is really practical. I guess I could do something like (gnus-summary-insert-old-articles 200) instead and hope that is good enough. Any thoughts on this?
--
Christopher Howard
next prev parent reply other threads:[~2025-01-09 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 22:44 bug#75329: 30.0.93; gnus: lowering thread score doesn't work on e-mail threads (...?) Christopher Howard
2025-01-09 3:23 ` Mike Kupfer
2025-01-09 16:18 ` Christopher Howard [this message]
2025-01-09 19:26 ` Mike Kupfer
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sepshsfs.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=75329@debbugs.gnu.org \
--cc=kupfer@rawbw.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).