unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Trevor Jim <tjim@mac.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: nevermore
Date: Wed, 16 Jul 2014 14:51:24 +0000 (GMT)	[thread overview]
Message-ID: <74f07268-8018-4790-885c-27f0dfb6733c@me.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

If you would like to incorporate things into the main branch, that would be great. Here's what I think the status is:

The asynchronous mail address harvesting works pretty well. Much better than having to install python etc. It would be better to also update the addresses when sending mail.

I imagine many people want to use something other than company-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 incremental search in mind. For example, I have to kill and start a new process 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 incremental 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 faster.) Notmuch, of course, is thread-focused.

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

-Trevor


[-- Attachment #2.1: Type: text/html, Size: 1692 bytes --]

             reply	other threads:[~2014-07-16 14:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 14:51 Trevor Jim [this message]
2014-07-29 16:57 ` nevermore Michal Sojka
2014-07-29 16:57   ` [PATCH RFC] Emacs: Add address completion mechanism implemented in elisp Michal Sojka
2014-07-30  1:20     ` David Bremner
2014-07-30 20:41       ` Michal Sojka
2014-07-31 23:44     ` David Bremner
2014-08-11 14:31       ` Michal Sojka
  -- strict thread matches above, loose matches on Subject: below --
2014-07-10 19:17 nevermore Trevor Jim
2014-07-15 10:20 ` nevermore David Bremner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=74f07268-8018-4790-885c-27f0dfb6733c@me.com \
    --to=tjim@mac.com \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).