From: Andrew Cohen <cohen@bu.edu>
To: info-gnus-english@gnu.org
Subject: Re: Finding last messages in a thread
Date: Fri, 01 May 2020 08:27:25 +0800 [thread overview]
Message-ID: <871ro4wlci.fsf@ust.hk> (raw)
In-Reply-To: <87imhglirg.fsf@web.de>
>>>>> "MH" == Michael Heerdegen <michael_heerdegen@web.de> writes:
MH> Andrew Cohen <cohen@bu.edu> writes:
>> And...its broken (I think). Since I use "A T" I never tried "/
>> T". With a prefix arg its supposed to limit the summary buffer to
>> the articles in the thread, but it doesn't. I believe the
>> (interactive) expression is wrong, so that the prefix arg is
>> thrown away.
MH> Yes, looks like that. I wonder who has done that. Let's see:
MH> 03f6388892 Allow limiting gnus summary buffers to a thread
MH> committed by a certain "Andrew G Cohen". Hmm, never heard that
MH> name. Should we contact him?
Err, I'm pretty sure he is unavailable :)
Anyway, here is the fix to get the prefix-arg properly passed (I don't
have a current checkout of master and my local trees are a mess and I
don't have time to fix it all up, blah, blah, can someone push this for
me please:):
@@ -8698,7 +8556,8 @@ gnus-summary-limit-include-thread
When called interactively, ID is the Message-ID of the current
article. If thread-only is non-nil limit the summary buffer to
these articles."
- (interactive (list (mail-header-id (gnus-summary-article-header))))
+ (interactive (list (mail-header-id (gnus-summary-article-header))
+ current-prefix-arg))
(let ((articles (gnus-articles-in-thread
(gnus-id-to-thread (gnus-root-id id))))
;;we REALLY want the whole thread---this prevents cut-threads
_______________________________________________
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-05-01 0:28 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
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 [this message]
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=871ro4wlci.fsf@ust.hk \
--to=cohen@bu.edu \
--cc=info-gnus-english@gnu.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).