From: Matt Ford <matt@dancingfrog.co.uk>
Subject: Re: Showing Complete Active Threads
Date: 15 Mar 2006 00:48:11 +0000 [thread overview]
Message-ID: <m37j6wcz3o.fsf@bull.dancingfrog.co.uk> (raw)
In-Reply-To: <87acc0bu36.fsf@baldur.nicundtas.de>
Hi,
I was having trouble with this too. The following post describes the behaviour of the 'some and 't options and explains a lot.
http://groups.google.co.uk/group/gnu.emacs.gnus/browse_thread/thread/7c3cc8b63a45514c/4481cd0a00002013?lnk=st&q=gnus-fetch-old-headers&rnum=7&hl=en#4481cd0a00002013
A point to note is that (IMHO) A T will only show the complete thread of an article up to the post is was executed over (this caused me a lot of confusion when testing as I'd made assumptions about the A T command). To test I ticked the original post in this thread and exited and came back into the group - hitting A T does nothing. Marking any subsequent post in the thread and hitting A T gets all posts it knows about up until that point (the current last post will show you everything).
It could be argued that as "I KNOW" that the top level post has replies and I've marked them as read then hittting A T (or some other command) should redisplay them. Whether this is implementable I don't know...certainly I'd like that behaviour.
Matt.
next prev parent reply other threads:[~2006-03-15 0:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 6:07 Rolleston
2006-03-08 8:38 ` Tassilo Horn
2006-03-08 18:53 ` Rolleston
2006-03-08 19:43 ` Tassilo Horn
2006-03-08 20:50 ` Rolleston
2006-03-08 22:45 ` Tassilo Horn
2006-03-12 23:04 ` Rolleston
2006-03-09 11:31 ` Gnus fetches too many headers WAS: " Tassilo Horn
2006-05-14 15:43 ` Dale Worley
2006-05-14 18:33 ` Tassilo Horn
2006-05-15 7:07 ` Frank Schmitt
2006-05-15 7:48 ` Tassilo Horn
2006-03-15 0:48 ` Matt Ford [this message]
2006-03-15 1:08 ` Matt Ford
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=m37j6wcz3o.fsf@bull.dancingfrog.co.uk \
--to=matt@dancingfrog.co.uk \
/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).