From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: info-gnus-english@gnu.org
Subject: Re: Finding last messages in a thread
Date: Wed, 29 Apr 2020 22:29:11 -0700 [thread overview]
Message-ID: <87ees5h788.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87h7x160n7.fsf@web.de> (Michael Heerdegen's message of "Thu, 30 Apr 2020 06:46:52 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Elsewhere the gnus code does this with `gnus-root-id', but I have no
>> idea if that is any faster or more convenient than your version (I would
>> be curious to know). I wonder if you could use the
>> `gnus-newsgroup-dependencies' hashtable.
>
> Maybe, I didn't invest too much time.
>
> But - I didn't miss any already existing method to reach my goal
> (finding the chronologically last messages in a thread)?
No, not that I'm aware of (mind you, I "discover" new Gnus functions
every few days).
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-04-30 5:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 3:15 Michael Heerdegen
2020-04-30 4:16 ` Eric Abrahamsen
2020-04-30 4:46 ` Michael Heerdegen
2020-04-30 5:29 ` Eric Abrahamsen [this message]
2020-04-30 5:31 ` Lars Ingebrigtsen
2020-04-30 7:01 ` Andrew Cohen
2020-04-30 8:25 ` Andrew Cohen
2020-04-30 22:18 ` Michael Heerdegen
2020-05-01 0:27 ` Andrew Cohen
2020-05-01 1:27 ` Michael Heerdegen
2020-05-01 2:12 ` Andrew Cohen
2020-04-30 20:36 ` Achilles Yuce
2020-04-30 20:45 ` Michael Heerdegen
2020-04-30 20:52 ` Achilles Yuce
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=87ees5h788.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.org \
--cc=michael_heerdegen@web.de \
/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).