Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH 2/2] nnir.el: New `notmuch' backend.
Date: Wed, 06 Apr 2011 08:22:45 -0500	[thread overview]
Message-ID: <87mxk3qztm.fsf@lifelogs.com> (raw)
In-Reply-To: <m2wrj7ykrr.fsf@ecocode.net>

On Wed, 06 Apr 2011 08:08:24 +0200 Erik Colson <eco@ecocode.net> wrote: 

EC> One remaining issue is searching the mailboxes through the IMAP
EC> server. It works, but it is slow due to the slowness of the IMAP
EC> server. So my wish would be to have a _local_ index of the distant mail
EC> on the IMAP server, without having a local cache of all the mails.

EC> Probably it would be preferable to have a separate process running a
EC> IMAP client which would read all new mails and index them locally. If
EC> anyone knows of such a software, please tell me!

It's probably easier to use the Gnus registry for local searching after
the recent rewrite.  For instance there's a
`gnus-registry-wash-for-keywords' function which will store all the
keywords for an article in the registry, and IIRC nnir has some glue for
it as well.

Once you are tracking keywords (set up with
`gnus-registry-track-extra'), any keywords noticed in an article will
end up indexed.  So then you just say

(registry-lookup-secondary-value gnus-registry-db 'keyword "thekeyword")

and you'll get a list of message IDs (which you can then look up to get
the group).  The nice thing is that when you set this up, it works
anytime you visit a group so it doesn't require external processes or
indices.  And it's using hashtables so it's a very fast lookup.

It would not be hard to use the notmuch keywords instead of the keywords
from the article body, if they are in the headers or connected to the
message ID somehow.  But I don't know notmuch well enough to do it.

Ted




  reply	other threads:[~2011-04-06 13:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 14:48 [PATCH 1/2] nnir.el (nnir-read-server-parm): Use default value Kan-Ru Chen
2011-04-03 14:48 ` [PATCH 2/2] nnir.el: New `notmuch' backend Kan-Ru Chen
2011-04-03 17:43   ` Lars Magne Ingebrigtsen
2011-04-04  1:04     ` Kan-Ru Chen
2011-04-04 13:43     ` Ted Zlatanov
2011-04-05  1:02       ` Kan-Ru Chen
2011-04-05 14:34         ` Ted Zlatanov
2011-04-06  6:08           ` Erik Colson
2011-04-06 13:22             ` Ted Zlatanov [this message]
2011-04-06  8:12           ` Kan-Ru Chen
2011-04-06  9:30       ` Julien Danjou
2011-07-04 16:09     ` Kan-Ru Chen
2011-07-05 20:22       ` Lars Magne Ingebrigtsen
2013-01-09 16:40         ` Gour
2013-08-01 22:14           ` Lars Magne Ingebrigtsen
2013-08-02  1:28             ` Kan-Ru Chen (陳侃如)

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

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

  git send-email \
    --in-reply-to=87mxk3qztm.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).