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 13:56:55 -0400 [thread overview]
Message-ID: <87r5fuc6xk.fsf@andy.bu.edu> (raw)
In-Reply-To: <m3d3re101u.fsf@quimbies.gnus.org>
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Andrew Cohen <cohen@andy.bu.edu> writes:
>> 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.
Lars> I think, perhaps, that it would be nice if this worked
Lars> generally for all non-NOV backends. Although the speedup for
Lars> IMAP is nice, but it should probably be refactored out into a
Lars> -request-thread function that would just return the headers of
Lars> all the articles that are in the thread.
I definitely agree and started thinking about this while playing around
with A T.
Firstly, this may be beyond my minimal skill set. But in any case, I
wonder what the backend functions should do. They could return the
headers as you suggest. Or they might just return the list of
articles. But I noticed that there is an imap extension for returning a
threaded list of messages. It might be useful to choose something that
would allow for backend specific speedups in threading.
Since I haven't figured out exactly how threading works at the moment,
I'm not sure whats best.
Regards,
Andy
next prev parent reply other threads:[~2010-10-13 17:56 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
2010-10-13 15:42 ` Julien Danjou
2010-10-13 17:21 ` Lars Magne Ingebrigtsen
2010-10-13 17:56 ` Andrew Cohen [this message]
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=87r5fuc6xk.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).