1 Return-Path: <dme@dme.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 1B914431FAF
\r
6 for <notmuch@notmuchmail.org>; Fri, 5 Sep 2014 09:06:23 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id v7BcX0n5s7+8 for <notmuch@notmuchmail.org>;
\r
16 Fri, 5 Sep 2014 09:06:17 -0700 (PDT)
\r
17 Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com
\r
18 [74.125.82.47]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client
\r
19 certificate requested) by olra.theworths.org (Postfix) with ESMTPS id
\r
20 46EFB431FB6 for <notmuch@notmuchmail.org>; Fri, 5 Sep 2014 09:06:17 -0700
\r
22 Received: by mail-wg0-f47.google.com with SMTP id z12so11780786wgg.6
\r
23 for <notmuch@notmuchmail.org>; Fri, 05 Sep 2014 09:06:14 -0700 (PDT)
\r
24 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
25 d=1e100.net; s=20130820;
\r
26 h=x-gm-message-state:to:subject:in-reply-to:references:user-agent
\r
27 :from:date:message-id:mime-version:content-type;
\r
28 bh=hErSz26R6eGDkX6aAJF4DmUCm2ufy2ns21KH+lxonDM=;
\r
29 b=mUZFfsl+nr7uRga3CGe/kvkTfJPEStjWNxi0vpRaAUI+5YzwncHV9KXPTinLjg5IUl
\r
30 DazY2s6BkuJiD7u2T2XOS9oZkaG0aLYO5253aXxw2eMp7Zeq/4+dpvu0iNYdedhP/26g
\r
31 N9w0QuV5aObnSV/ezfiTxJoJual/D8GUgD/bVpP+dPO9hCNHuFyvcdSjPjyfinH/qDPq
\r
32 iEu2lKNhU4jNWh5ulSp0PbCbBY8r+au+uLa8Vxyz/XuXLoqx3OWBftXWnfwNnxGeGggs
\r
33 Fr04Qc6vcwrqH5Vrs9Z0fRPMfB+tz/8ZbPL4Ev1I9co2ebXR50eqOSGBUJWEcrzIDFx5
\r
36 ALoCoQmDSNquwT/WZzxQ18GPVzNZ7L+GAe6gi/RtHkO8myrsK+nJpGqJ+YAF9yftgOWGlUlUq4mL
\r
37 X-Received: by 10.194.187.241 with SMTP id fv17mr16262486wjc.13.1409933174699;
\r
38 Fri, 05 Sep 2014 09:06:14 -0700 (PDT)
\r
39 Received: from localhost ([2a01:348:1a2:1:4559:6492:4175:6b36])
\r
40 by mx.google.com with ESMTPSA id m9sm1851363wjz.35.2014.09.05.09.06.13
\r
41 for <multiple recipients>
\r
42 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
\r
43 Fri, 05 Sep 2014 09:06:14 -0700 (PDT)
\r
44 To: Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
\r
45 Subject: Re: [PATCH v1 0/3] Address completion entirely in elisp.
\r
46 In-Reply-To: <87k35igk5n.fsf@qmul.ac.uk>
\r
47 References: <1409921969-65129-1-git-send-email-dme@dme.org>
\r
48 <87k35igk5n.fsf@qmul.ac.uk>
\r
49 User-Agent: Notmuch/0.18.1 (http://notmuchmail.org) Emacs/24.3.1
\r
50 (x86_64-apple-darwin)
\r
51 From: David Edmondson <dme@dme.org>
\r
52 Date: Fri, 05 Sep 2014 17:06:12 +0100
\r
53 Message-ID: <m2y4tygih7.fsf@dme.org>
\r
55 Content-Type: text/plain
\r
56 X-BeenThere: notmuch@notmuchmail.org
\r
57 X-Mailman-Version: 2.1.13
\r
59 List-Id: "Use and development of the notmuch mail system."
\r
60 <notmuch.notmuchmail.org>
\r
61 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
62 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
63 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
64 List-Post: <mailto:notmuch@notmuchmail.org>
\r
65 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
66 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
67 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
68 X-List-Received-Date: Fri, 05 Sep 2014 16:06:23 -0000
\r
70 On Fri, Sep 05 2014, Mark Walters wrote:
\r
71 > On Fri, 05 Sep 2014, David Edmondson <dme@dme.org> wrote:
\r
72 >> Address completion entirely in elisp.
\r
74 >> I grew frustrated with having to use an external command to provide
\r
75 >> address completion, as they all had annoyances (up front scanning,
\r
76 >> requiring python bindings, etc.). This is an attempt to provide
\r
77 >> something similar to jkr's notmuch-addresses.py (which I was
\r
78 >> previously using) entirely in elisp, relying only on the `notmuch'
\r
81 > Just a few quick comments: the first is relevant to others trying this
\r
84 > 1) You seem to be missing a (require 'std11) somewhere. I did this via M-:
\r
85 > and then it ran fine.
\r
87 My apologies. Will fix (and a compiler warning at the same time).
\r
89 > 2) It is not quick on a spinning rust disk. This may not be relevant as
\r
90 > the delay is probably notmuch so would also be the case if I were using
\r
91 > notmuch-addresses.py (i normally just use a trivial script that parses
\r
94 It's not always as fast as I would like on SSD either :-) The mechanism
\r
95 is very similar to the equivalent Python program, so I think that it's
\r
96 probably about the same.
\r
99 > id:1407771091-12651-1-git-send-email-sojkam1@fel.cvut.cz and do you have
\r
100 > any comments on the comparison?
\r
102 No, I will dig it out and look.
\r
104 > 4) Finally, I wonder if we would be worth approaching the backend
\r
105 > notmuch use slightly differently: if we added a
\r
106 > notmuch_messages_collect_from function which was very similar to
\r
107 > notmuch_messages_collect_tags, and added a corresponding --output=from
\r
108 > to notmuch search then you would get the information you need very
\r
109 > quickly. I think it might be a lot faster as I think the from header is
\r
110 > stored in the database but some other headers are not, so that the
\r
111 > current method the show --body=false needs to look at the actually
\r
114 Extending notmuch to help with this was next on my list of things to
\r
115 do. At the moment I just needed a solution that worked.
\r
117 > I should emphasise that none of the above means I am opposed to the
\r
118 > patch: having respectable built in address-completion support would be
\r