From: Matt Ford <matt@dancingfrog.co.uk>
To: ding@gnus.org
Subject: Re: Referring threads seems inconsistent...
Date: Thu, 06 Mar 2014 15:02:48 +0000 [thread overview]
Message-ID: <87txbbv087.fsf@rss01.mhs.man.ac.uk> (raw)
In-Reply-To: <87d2i0tv1g.fsf@building.gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> It's not clear to me what you want to have happen. >"?
>
> Does `gnus-fetch-old-headers' do what you expect?
Upon first entering a group with unread or flagged messages then running
A T on one of these messages does not pull in the rest of the thread.
A T only seems to works if the whole group is loaded first or if all older
messages are pulled in with / o. But this kinda defeats the purpose.
Hope that's a bit clearer.
--
Matt
next prev parent reply other threads:[~2014-03-06 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 12:23 Matt Ford
2014-03-05 17:27 ` Lars Ingebrigtsen
2014-03-06 15:02 ` Matt Ford [this message]
2014-03-06 15:22 ` Andrew Cohen
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=87txbbv087.fsf@rss01.mhs.man.ac.uk \
--to=matt@dancingfrog.co.uk \
--cc=ding@gnus.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).