From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH 2/2] nnir.el: New `notmuch' backend.
Date: Tue, 05 Apr 2011 09:34:36 -0500 [thread overview]
Message-ID: <874o6c7on7.fsf@lifelogs.com> (raw)
In-Reply-To: <87hbad1pes.fsf@anar.kanru.info>
On Tue, 05 Apr 2011 09:02:19 +0800 Kan-Ru Chen <kanru@kanru.info> wrote:
KC> Hey! I understand Julien's concern of notmuch but there is one thing
KC> notmuch does besides tagging mail, that is index the mail using xapian
KC> engine. Actually this is all what notmuch can do, plus some MUA friendly
KC> interface so MUAs like mutt or Gnus can use it as a index engine.
KC> I'm still using nnml backend, so nnir is really import to me. I have
KC> experience with notmuch, it is easier to configure than namazu or
KC> swish++ so I think it is a good idea to put notmuch support into Gnus.
I have no problem with notmuch support in Gnus, just wondered if Julien
had comments since he has dealt with the software.
To me it seems useful and I can see how the Gnus registry marks could
synchronize with the notmuch tags. spam.el could use notmuch tags as
well.
Ted
next prev parent reply other threads:[~2011-04-05 14:34 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 [this message]
2011-04-06 6:08 ` Erik Colson
2011-04-06 13:22 ` Ted Zlatanov
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=874o6c7on7.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).