1 Return-Path: <david@tethera.net>
\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 arlo.cworth.org (Postfix) with ESMTP id 3616F6DE0243
\r
6 for <notmuch@notmuchmail.org>; Fri, 3 Jun 2016 16:13:03 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at cworth.org
\r
11 X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5
\r
12 tests=[AWL=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]
\r
14 Received: from arlo.cworth.org ([127.0.0.1])
\r
15 by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id hL5v-2qL8c7f for <notmuch@notmuchmail.org>;
\r
17 Fri, 3 Jun 2016 16:12:55 -0700 (PDT)
\r
18 Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])
\r
19 by arlo.cworth.org (Postfix) with ESMTPS id 593BB6DE0159
\r
20 for <notmuch@notmuchmail.org>; Fri, 3 Jun 2016 16:12:55 -0700 (PDT)
\r
21 Received: from remotemail by fethera.tethera.net with local (Exim 4.84)
\r
22 (envelope-from <david@tethera.net>)
\r
23 id 1b8yGg-00041A-JZ; Fri, 03 Jun 2016 19:12:42 -0400
\r
24 Received: (nullmailer pid 32126 invoked by uid 1000);
\r
25 Fri, 03 Jun 2016 23:12:52 -0000
\r
26 From: David Bremner <david@tethera.net>
\r
27 To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
\r
28 Subject: Re: [RFC2 Patch 5/5] lib: iterator API for message properties
\r
29 In-Reply-To: <87y46mpcbf.fsf@alice.fifthhorseman.net>
\r
30 References: <1463927339-5441-1-git-send-email-david@tethera.net>
\r
31 <1464608999-14774-1-git-send-email-david@tethera.net>
\r
32 <1464608999-14774-6-git-send-email-david@tethera.net>
\r
33 <8760tthfuy.fsf@zancas.localnet> <87pos1u14p.fsf@alice.fifthhorseman.net>
\r
34 <87eg8ht2sb.fsf@alice.fifthhorseman.net> <87lh2ofpxk.fsf@zancas.localnet>
\r
35 <87inxrqyv1.fsf@alice.fifthhorseman.net> <8737oufn6f.fsf@zancas.localnet>
\r
36 <87y46mpcbf.fsf@alice.fifthhorseman.net>
\r
37 User-Agent: Notmuch/0.22+28~gb9bf3f4 (http://notmuchmail.org) Emacs/24.5.1
\r
38 (x86_64-pc-linux-gnu)
\r
39 Date: Fri, 03 Jun 2016 20:12:52 -0300
\r
40 Message-ID: <87mvn1euiz.fsf@zancas.localnet>
\r
42 Content-Type: text/plain
\r
43 X-BeenThere: notmuch@notmuchmail.org
\r
44 X-Mailman-Version: 2.1.20
\r
46 List-Id: "Use and development of the notmuch mail system."
\r
47 <notmuch.notmuchmail.org>
\r
48 List-Unsubscribe: <https://notmuchmail.org/mailman/options/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
50 List-Archive: <http://notmuchmail.org/pipermail/notmuch/>
\r
51 List-Post: <mailto:notmuch@notmuchmail.org>
\r
52 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
53 List-Subscribe: <https://notmuchmail.org/mailman/listinfo/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
55 X-List-Received-Date: Fri, 03 Jun 2016 23:13:03 -0000
\r
57 Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:
\r
59 > [ Unknown signature status ]
\r
60 > On Fri 2016-06-03 08:54:00 -0400, David Bremner wrote:
\r
61 >> Sure, where do you think that kind of documentation is appropriate?
\r
62 >> There is the giant comment about the database schema in
\r
63 >> lib/database.cc. Actually I just noticed I already failed to update that
\r
64 >> for libconfig stuff.
\r
66 > That comment seems OK, but it won't be exposed to the people who are in
\r
67 > that middle range (python or ruby programmers but not C programmers).
\r
68 > Do we have a place for this kind of mid-level documenation?
\r
70 The simplest solution is probably API documentation itself
\r
71 (lib/notmuch.h), which should propagage to the bindings documentation.
\r
72 Maybe I'll start with that, and we can go from there.
\r
76 >>> * for messages which have multiple files, which file is actually indexed
\r
78 >> yes. Although rather than storing that, I think the right answer is more
\r
79 >> like "all of them".
\r
81 > I don't think we do this, do we? Is this a bug? is it tracked somewhere?
\r
83 IMHO it is a bug. It's implicit in
\r
85 id:87k42vrqve.fsf@pip.fifthhorseman.net
\r
87 and the various requests for List-Id indexing, but it's probably worth
\r
88 starting a seperate thread to track it. Especially since there are some
\r
89 unresolved design issues. Like what to return for searches.
\r
91 > This is exactly my point -- i don't care about reproducibility of the
\r
92 > exact numbering, but , the thread-id is *not* reproducible from the
\r
93 > message sets. This is not only because of the ghost message leakage bug
\r
94 > documented in T590-thread-breakage.sh, but also because threads can be
\r
95 > joined by a message that is later removed (e.g., the "notmuch-join"
\r
96 > script in id:87egabu5ta.fsf@alice.fifthhorseman.net ).
\r
98 I see, I guess that's the intended behaviour given 604d1e0977c.
\r
100 I haven't thought about the pros and cons of dumping/restoring
\r
101 thread-ids. At least my database has about half as many threads as
\r
102 messages, so it's a bit of data, but perhaps that's not a bit problem.
\r
103 It's somewhat orthogonal to this series since those terms are already
\r
104 attached to messages.
\r
106 >> I'm not sure what you have in mind, something more ambitious than the
\r
107 >> header added post 0.22?
\r
109 > Can you point me to the definition for that header? i still don't
\r
110 > understand what the batch-tag:2 part means. (sorry i haven't been
\r
111 > keeping up with the master branch lately!)
\r
114 Currently there's just the source: it says which format, and with that
\r
115 format, which subset of output.
\r
118 print_dump_header (gzFile output, int output_format, int include)
\r
120 gzprintf (output, "#notmuch-dump %s:%d %s%s%s\n",
\r
121 (output_format == DUMP_FORMAT_SUP) ? "sup" : "batch-tag",
\r
122 NOTMUCH_DUMP_VERSION,
\r
123 (include & DUMP_INCLUDE_CONFIG) ? "config" : "",
\r
124 (include & DUMP_INCLUDE_TAGS) && (include & DUMP_INCLUDE_CONFIG) ? "," : "",
\r
125 (include & DUMP_INCLUDE_TAGS) ? "tags" : "");
\r
projects / notmuch-archives.git / blob