1 Return-Path: <cworth@cworth.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id D9D33431FC0;
\r
6 Fri, 27 Nov 2009 19:58:14 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id V2n7Dn6bLhKj; Fri, 27 Nov 2009 19:58:14 -0800 (PST)
\r
11 Received: from cworth.org (localhost [127.0.0.1])
\r
12 by olra.theworths.org (Postfix) with ESMTP id 2DECD431FAE;
\r
13 Fri, 27 Nov 2009 19:58:14 -0800 (PST)
\r
14 From: Carl Worth <cworth@cworth.org>
\r
15 To: Ruben Pollan <meskio@sindominio.net>, notmuch@notmuchmail.org
\r
16 In-Reply-To: <20091126202347.GA16654@blackspot>
\r
17 References: <20091126202347.GA16654@blackspot>
\r
18 Date: Fri, 27 Nov 2009 19:57:59 -0800
\r
19 Message-ID: <87pr73jo6w.fsf@yoom.home.cworth.org>
\r
21 Content-Type: text/plain; charset=us-ascii
\r
22 Subject: Re: [notmuch] notmuch_threads_back and notmuch_messages_back
\r
23 X-BeenThere: notmuch@notmuchmail.org
\r
24 X-Mailman-Version: 2.1.12
\r
26 List-Id: "Use and development of the notmuch mail system."
\r
27 <notmuch.notmuchmail.org>
\r
28 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
29 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
30 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
31 List-Post: <mailto:notmuch@notmuchmail.org>
\r
32 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
33 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
34 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
35 X-List-Received-Date: Sat, 28 Nov 2009 03:58:15 -0000
\r
37 On Thu, 26 Nov 2009 21:23:47 +0100, Ruben Pollan <meskio@sindominio.net> wrote:
\r
38 > Is it possible to implement notmuch_threads_back and notmuch_messages_back?
\r
39 > And I guess will make sense to have also notmuch_tags_back.
\r
41 > This functions will do the oposite than notmuch_threads_advance and
\r
42 > notmuch_messages_advance. So I can use them as iterators going back and forward.
\r
44 > I didn't check the implementation of notmuch. I don't know if will be easy or
\r
45 > will need to redesign a lot of code.
\r
47 Most cases of these iterators are built on Xapian iterators, (C++ objects with
\r
48 overloaded operators). So those are just using ++ for advance() and can
\r
49 easily use -- for the new function, (I'd like a verb that pairs better
\r
50 with "advance" than the non-verb "back"---any suggestions)?
\r
52 So those won't need any new code. The one case that will need new code
\r
53 is that for notmuch_message_get_replies and
\r
54 notmuch_message_get_toplevel_messages the messages iterator is currently
\r
55 built on a singly-linked list. Making it doubly linked would obviously
\r