From: Andrew Cohen <cohen@andy.bu.edu>
To: ding@gnus.org
Subject: Re: A T does not work in nnimap
Date: Wed, 13 Oct 2010 11:30:27 -0400 [thread overview]
Message-ID: <877hhmdsa4.fsf@andy.bu.edu> (raw)
In-Reply-To: <sa3pqvetcx0.fsf@cigue.easter-eggs.fr> (Julien Danjou's message of "Wed, 13 Oct 2010 15:55:39 +0200")
>>>>> "Julien" == Julien Danjou <julien@danjou.info> writes:
Julien> On Wed, Oct 13 2010, Andrew Cohen wrote:
>> OK here is a first pass at modifying gnus-summary-refer-thread to
>> work with imap. It seemed like a good idea to factor out a
>> thread-searching function for nnimap, so I did.
Julien> Looks good. The only problem I see is that when I press A T,
Julien> I then get *only* the thread I'm reading. It kicks all the
Julien> other messages out of the *Summary* buffer. :-(
In fact I'm suspecting that this has uncovered an underlying bug. Just
to make sure its not me, can you go to an nntp group which is displaying
only one message from some multi-message thread in the summary buffer
and try A T? For me it doesn't incorporate the rest of the thread.
[...]
Julien> I'm not sure such a backend check is welcome here. Isn't
Julien> there a more generic way to handle that?
Well, I should probably do
(eq (car gnus-find-method-for-group group) 'nnimap)
This seems to be what is used generically for checking the backend
method. I'll make this change.
Thanks,
Andy
next prev parent reply other threads:[~2010-10-13 15:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 11:00 Julien Danjou
2010-10-07 18:13 ` Lars Magne Ingebrigtsen
2010-10-12 13:28 ` Julien Danjou
2010-10-12 13:50 ` Lars Magne Ingebrigtsen
2010-10-12 14:18 ` Julien Danjou
2010-10-12 14:43 ` Andrew Cohen
2010-10-12 23:43 ` Andrew Cohen
2010-10-13 13:55 ` Julien Danjou
2010-10-13 15:30 ` Andrew Cohen [this message]
2010-10-13 15:42 ` Julien Danjou
2010-10-13 17:21 ` Lars Magne Ingebrigtsen
2010-10-13 17:56 ` Andrew Cohen
2010-10-13 18:29 ` Lars Magne Ingebrigtsen
2010-10-13 20:59 ` Andrew Cohen
2010-10-13 21:11 ` Lars Magne Ingebrigtsen
2010-10-13 21:30 ` Andrew Cohen
2010-10-13 21:37 ` Lars Magne Ingebrigtsen
2010-10-13 21:59 ` Andrew Cohen
2010-10-13 22:06 ` Lars Magne Ingebrigtsen
2010-10-14 0:38 ` Andrew Cohen
2010-10-14 12:57 ` Andrew Cohen
2010-10-14 18:00 ` Lars Magne Ingebrigtsen
2010-10-14 18:45 ` Andrew Cohen
2010-10-14 19:02 ` Lars Magne Ingebrigtsen
2010-10-15 11:02 ` Julien Danjou
2010-10-15 11:24 ` Andrew Cohen
2010-10-15 11:29 ` Julien Danjou
2010-10-15 11:53 ` Steinar Bang
2010-10-15 12:01 ` Julien Danjou
2010-10-15 12:00 ` Andrew Cohen
2010-10-15 12:06 ` Julien Danjou
2010-10-15 12:17 ` Andrew Cohen
2010-10-15 12:26 ` Andrew Cohen
2010-10-15 18:26 ` Julien Danjou
2010-10-16 12:58 ` Andrew Cohen
2010-10-16 18:16 ` Lars Magne Ingebrigtsen
2010-10-15 14:03 ` Lars Magne Ingebrigtsen
2010-10-15 12:11 ` Andrew Cohen
2010-10-15 12:28 ` Julien Danjou
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=877hhmdsa4.fsf@andy.bu.edu \
--to=cohen@andy.bu.edu \
--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).