From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/73077 Path: news.gmane.org!not-for-mail From: Andrew Cohen Newsgroups: gmane.emacs.gnus.general Subject: Re: A T does not work in nnimap Date: Wed, 13 Oct 2010 16:59:14 -0400 Message-ID: <87hbgpdd25.fsf@andy.bu.edu> References: <874ocrwjxu.fsf@andy.bu.edu> <87mxqjvuy8.fsf@andy.bu.edu> <87r5fuc6xk.fsf@andy.bu.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1287003598 19192 80.91.229.12 (13 Oct 2010 20:59:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 13 Oct 2010 20:59:58 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M21449@lists.math.uh.edu Wed Oct 13 22:59:57 2010 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1P68QW-0007R8-JF for ding-account@gmane.org; Wed, 13 Oct 2010 22:59:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1P68Q6-00030h-TF; Wed, 13 Oct 2010 15:59:30 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1P68Q4-00030P-UP for ding@lists.math.uh.edu; Wed, 13 Oct 2010 15:59:28 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1P68Q0-0004XB-H7 for ding@lists.math.uh.edu; Wed, 13 Oct 2010 15:59:28 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1P68Py-0004n7-00 for ; Wed, 13 Oct 2010 22:59:22 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1P68Py-0007Cr-JO for ding@gnus.org; Wed, 13 Oct 2010 22:59:22 +0200 Original-Received: from andy.bu.edu ([128.197.41.152]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 13 Oct 2010 22:59:22 +0200 Original-Received: from cohen by andy.bu.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 13 Oct 2010 22:59:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 34 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: andy.bu.edu User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:hOPhjiqL+L9rKyLx6PEbI04/ivQ= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:73077 Archived-At: >>>>> "Lars" == Lars Magne Ingebrigtsen writes: Lars> Andrew Cohen writes: >> 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. Lars> Gnus does its own threading according to its own algo. It's Lars> better to just return a buffer full of article headers and let Lars> Gnus do its magic. OK. Like I said, probably beyond my skill set, but I'm still trying. Once I have retrieved the headers (gnus-retrieve-headers), how do I get them incorporated into the thread? I think I see how to do this with NOV, but not with the full headers in the nnimap-buffer. The existing gnus-summary-refer-thread doesn't work very well even for nntp groups. For example I have one of Julien's messages in this thread ticked (the only ticked message in gnus.general). If I enter the group this is the only message showing in the summary buffer. If I then 'A T' on this message, I get a subset of thread only. From what I can tell the existing code tries to download a whole bunch of headers and simply hopes that the full thread is present. Sometimes it is, and sometimes it isn't. I can guarantee the full thread in nnimap, but only if I do something special for the nnimap backend, which I think we would like to avoid. Regards, Andy