From: Matt Ford <matt@dancingfrog.co.uk>
To: ding@gnus.org
Subject: Referring threads seems inconsistent...
Date: Fri, 14 Feb 2014 12:23:15 +0000 [thread overview]
Message-ID: <87bny93mto.fsf@rss01.mhs.man.ac.uk> (raw)
Hi,
I try to leave but always end up coming back to GNUs :-)
So, I have a bunch of flagged emails in my nnimap back-end. When I
visit the group only the flagged mails are listed. For a bit more
context I hit A-T and sometimes nothing happens and other times it fills my
thread beautifully.
I can make the thread filling work very nicely if I do a / o followed by
/ w - subsequent issues of A T work well. I guess this some how caches
the threads and subsequent queries work.
Alternately I can do C-u Return and / m ! and then run the A T. This
first gets the whole group and then limits the display back to the
marked articles.
Is there anyway I can make things work on normal entry. Is this a bug?
I'm using Plugged by the way. Perhaps its interaction affects things?
That's a guess.
Any thoughts?
Cheers,
--
Matt
next reply other threads:[~2014-02-14 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 12:23 Matt Ford [this message]
2014-03-05 17:27 ` Lars Ingebrigtsen
2014-03-06 15:02 ` Matt Ford
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=87bny93mto.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).