From: Matt McClure <matthew.mcclure.es.99@aya.yale.edu>
Subject: A T only finds old articles in current thread
Date: 29 Sep 1999 11:20:44 -0400 [thread overview]
Message-ID: <hpemfheoc3.fsf@shell.faradic.net> (raw)
The documentation for gnus-summary-refer-thread says:
A T runs the command gnus-summary-refer-thread
which is an interactive compiled Lisp function in `gnus-sum'.
(gnus-summary-refer-thread &optional LIMIT)
Fetch all articles in the current thread.
If LIMIT (the numerical prefix), fetch that many old headers instead
of what's specified by the `gnus-refer-thread-limit' variable.
But it appears to find only old articles in the current thread. For
example, suppose I have ticked an article, I subsequently read a follow-up
to it, exit the group, then re-enter later. The ticked article will
show in the summary, but not the follow-up. I would expect A T to find
the whole thread, including the follow-up to the ticked article, but it
only finds older articles.
Is there any way to find the _entire_ thread?
Thanks,
Matt
--
--------------------------------------
| matthew.mcclure.es.99@aya.yale.edu |
| http://www.faradic.net/~mmcclure |
--------------------------------------
next reply other threads:[~1999-09-29 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 15:20 Matt McClure [this message]
1999-11-06 1:44 ` Lars Magne Ingebrigtsen
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=hpemfheoc3.fsf@shell.faradic.net \
--to=matthew.mcclure.es.99@aya.yale.edu \
/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).