From: Niklas Morberg <niklas.morberg@axis.com>
Cc: ding@gnus.org
Subject: Re: nnir and fast email searches
Date: Mon, 05 Jul 2004 08:03:59 +0200 [thread overview]
Message-ID: <xiubrivkn1s.fsf@lnxniklas.se.axis.com> (raw)
In-Reply-To: <r77wu1jjroy.fsf@muscadet.inria.fr> (James Leifer's message of "Mon, 05 Jul 2004 01:09:01 +0200")
James Leifer <James.Leifer@inria.fr> writes:
> I run a nightly cron job that indexes all my mail, which consists of
> about 30K messages stored in maildir or mh format (one file per
> message). The indexing is performed by swish++ which is easy to get
> and available prepackaged under Debian woody and many other distros.
>
> When I want to search, I populate a directory with symlinks to the
> messages swish++ returns.
Would you care to share the code you have to achieve this?
Also, how do read the messages from within gnus?
> I believe nnir.el can use swish++, though I don't know nnir.el well.
I tried to get this working, but failed. See [tedious
searching at gmane.org] thread
<URL:http://thread.gmane.org/gmane.emacs.gnus.general/57947>
I started using the agent to fetch messages (I'm using
imap), but that was not as smooth as I wanted (too slow and
somewhat inconsistent behaviour -- I needed to delete the
agent hierarchy and restart a couple of times). Instead I'm
planning on using offlineimap and then index them using a
search engine.
The remaining problem is to integrate the search results
with gnus.
By the way, Zoe <URL:http://www.zoe.nu> is really nice.
Works like a charm and without much hassle. Its main
problems are no integration with gnus and slowness when your
search yields many results.
Niklas
next prev parent reply other threads:[~2004-07-05 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 22:37 Max Froumentin
2004-07-04 23:09 ` James Leifer
2004-07-05 6:03 ` Niklas Morberg [this message]
2004-07-05 7:43 ` James Leifer
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=xiubrivkn1s.fsf@lnxniklas.se.axis.com \
--to=niklas.morberg@axis.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).