From: Trevor Jim Date: Wed, 16 Jul 2014 14:51:24 +0000 (+0000) Subject: Re: nevermore X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=f06864beee32d5fac0d88260fd147fb436b71bf3;p=notmuch-archives.git Re: nevermore --- diff --git a/7e/795b98797daa43a530b48e55487cf1b214c671 b/7e/795b98797daa43a530b48e55487cf1b214c671 new file mode 100644 index 000000000..ccc1ad8f1 --- /dev/null +++ b/7e/795b98797daa43a530b48e55487cf1b214c671 @@ -0,0 +1,133 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id E514E431FC3 + for ; Wed, 16 Jul 2014 07:51:37 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Spam-Flag: NO +X-Spam-Score: -2.297 +X-Spam-Level: +X-Spam-Status: No, score=-2.297 tagged_above=-999 required=5 + tests=[FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, + MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id MkfLykdK9nhK for ; + Wed, 16 Jul 2014 07:51:31 -0700 (PDT) +Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtp001.mac.com + [17.172.220.236]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 9E895431FBD + for ; Wed, 16 Jul 2014 07:51:31 -0700 (PDT) +MIME-version: 1.0 +Content-type: multipart/alternative; + boundary="Boundary_(ID_9a3eFww91i+V0AqUg063OA)" +Received: from st11p02mm-spool002.mac.com ([17.172.220.247]) + by st11p02mm-asmtp001.mac.com + (Oracle Communications Messaging Server 7u4-27.10(7.0.4.27.9) 64bit + (built Jun + 6 2014)) with ESMTP id <0N8T00GJP7XONS80@st11p02mm-asmtp001.mac.com> + for notmuch@notmuchmail.org; Wed, 16 Jul 2014 14:51:24 +0000 (GMT) +X-Proofpoint-Virus-Version: vendor=fsecure + engine=2.50.10432:5.12.52,1.0.14,0.0.0000 + definitions=2014-07-16_05:2014-07-16, 2014-07-16, + 1970-01-01 signatures=0 +X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 + suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam + adjust=0 + reason=mlx scancount=1 engine=7.0.1-1402240000 + definitions=main-1407160173 +Received: from localhost ([17.172.220.163]) by st11p02mm-spool002.mac.com + (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit + (built Aug + 22 2013)) with ESMTP id <0N8T00DCU7XOZF00@st11p02mm-spool002.mac.com>; + Wed, 16 Jul 2014 14:51:24 +0000 (GMT) +To: David Bremner +From: Trevor Jim +Subject: Re: nevermore +Date: Wed, 16 Jul 2014 14:51:24 +0000 (GMT) +X-Mailer: iCloud MailClient14D29 MailServer14E24.16380 +X-Originating-IP: [128.112.139.195] +Message-id: <74f07268-8018-4790-885c-27f0dfb6733c@me.com> +X-Mailman-Approved-At: Sun, 20 Jul 2014 13:32:26 -0700 +Cc: notmuch@notmuchmail.org +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Wed, 16 Jul 2014 14:51:38 -0000 + + +--Boundary_(ID_9a3eFww91i+V0AqUg063OA) +Content-type: text/plain; charset=utf-8; format=flowed +Content-transfer-encoding: quoted-printable + +If you would like to incorporate things into the main branch, that would b= +e great. Here's what I think the status is:=0A=0AThe asynchronous mail add= +ress harvesting works pretty well. Much better than having to install pyth= +on etc. It would be better to also update the addresses when sending mail.= +=0A=0AI imagine many people want to use something other than company-mode,= + though. Probably needs testing for other completion systems.=0A=0AThe inc= +remental search works well for me, but I think it needs testing on larger = +maildirs. Notmuch as it exists today does not seem to have incremental sea= +rch in mind. For example, I have to kill and start a new process each time= + the search term changes (potentially on each keystroke).=0A=0AMy async pa= +rsing is noticeably faster than notmuch.el, so you might want to incorpora= +te some of its ideas, regardless of whether you take incremental search.=0A= +=0AOne complication of the incremental search code is that I like to query= + based on messages rather than threads. Both are actually useful, but I'm = +happier with messages. (For one thing, it should be much faster.) Notmuch,= + of course, is thread-focused.=0A=0AFor message-based search, --output=3Ds= +ummary is not appropriate, even if the query is a message-id; the result i= +ncludes, for example, tags that appear only in other messages in the threa= +d. So I have been forced to use notmuch show --body=3Dfalse instead. This = +precludes other useful options of notmuch search, e.g., --sort. Anyway, th= +e incremental search code has some complications for this. I'd love for no= +tmuch search to have a --output=3Dmessage-summary option to avoid this.=0A= +=0A-Trevor=0A=EF=BB=BF=0A= + +--Boundary_(ID_9a3eFww91i+V0AqUg063OA) +Content-type: multipart/related; + boundary="Boundary_(ID_bMCoUUu9DlyD+gmZQEu3fg)"; type="text/html" + + +--Boundary_(ID_bMCoUUu9DlyD+gmZQEu3fg) +Content-type: text/html; CHARSET=US-ASCII +Content-transfer-encoding: quoted-printable + +
If you would like to incorporate things into the main branch, that wo= +uld be great. Here's what I think the status is:

The asynchronous m= +ail address harvesting works pretty well. Much better than having to insta= +ll python etc. It would be better to also update the addresses when sendin= +g mail.

I imagine many people want to use something other than comp= +any-mode, though. Probably needs testing for other completion systems.
= +
The incremental search works well for me, but I think it needs testing= + on larger maildirs. Notmuch as it exists today does not seem to have incr= +emental search in mind. For example, I have to kill and start a new proces= +s each time the search term changes (potentially on each keystroke).
My async parsing is noticeably faster than notmuch.el, so you might want= + to incorporate some of its ideas, regardless of whether you take incremen= +tal search.

One complication of the incremental search code is that= + I like to query based on messages rather than threads. Both are actually = +useful, but I'm happier with messages. (For one thing, it should be much f= +aster.) Notmuch, of course, is thread-focused.

For message-based se= +arch, --output=3Dsummary is not appropriate, even if the query is a messag= +e-id; the result includes, for example, tags that appear only in other mes= +sages in the thread. So I have been forced to use notmuch show --body=3Dfa= +lse instead. This precludes other useful options of notmuch search, e.g., = +--sort. Anyway, the incremental search code has some complications for thi= +s. I'd love for notmuch search to have a --output=3Dmessage-summary option= + to avoid this.

-Trevor

= + +--Boundary_(ID_bMCoUUu9DlyD+gmZQEu3fg)-- + +--Boundary_(ID_9a3eFww91i+V0AqUg063OA)--