From: Andrew Cohen <cohen@bu.edu>
To: info-gnus-english@gnu.org
Subject: Re: Finding last messages in a thread
Date: Thu, 30 Apr 2020 16:25:44 +0800 [thread overview]
Message-ID: <87h7x14bxz.fsf@ust.hk> (raw)
In-Reply-To: <87pnbpihia.fsf@ust.hk>
>>>>> "AC" == Andrew Cohen <cohen@bu.edu> writes:
>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
LI> Michael Heerdegen <michael_heerdegen@web.de> writes:
>>> I guessed the quickest way could be to limit to the current
>>> thread (???), and then turn off threading (C-M-t), but the first
>>> functionality doesn't seem to exist, so I implemented it quicky:
LI> Limiting to a thread seems like a natural thing to do, but I
LI> can't find such a command, either. It seems like Gnus should
LI> have such a command.
AC> I think this already exists (bound to "/ T")
AC> (defun gnus-summary-limit-include-thread (id &optional
AC> thread-only) "Display all hidden articles belonging to thread
AC> ID. When called interactively, ID is the Message-ID of the
AC> current article. If thread-only is non-nil limit the summary
AC> buffer to these articles."
AC> What I typically do is "A T" (gnus-summary-refer-thread) which
AC> will additionally search for all the articles in the thread.
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.
_______________________________________________
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 8: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 [this message]
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=87h7x14bxz.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).