From: Alexander Baier <lexi.baier@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Create a group from a list of message-ids
Date: Mon, 25 Nov 2013 15:08:25 +0100 [thread overview]
Message-ID: <87d2loa812.fsf@gmail.com> (raw)
In-Reply-To: <87txf01uum.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 25 Nov 2013 20:20:17 +0700")
On 13-11-25 14:20 Eric Abrahamsen wrote:
> Alexander Baier <lexi.baier@gmail.com> writes:
[...]
>>
>> I did not yet give notmuch a look, could you point out what in your
>> opinion make notmuch more flexible than namazu?
>
> Hmm, I was afraid you'd ask that! :)
>
> As far as I can recall, the interface to namazu felt very slow, and the
> search syntax was much more awkward and limited than notmuch. Notmuch
> just feels easier to use: it caches recent queries, lets you filter
> previous queries more easily, and makes browsing the results quite easy
> -- it actually acts as its own little MUA, with threading and
> everything. (Actually that can be annoying when all you want is the
> original message.) Mairix can't do unicode indexing, so that was right
> out.
>
This sounds very nice! You mention notmuch comes with its own
MUA. Although this might be usefull in a lot of situations, I am looking
for something that can integrate with gnus. This means I would like to
have something, that displays the search results as a group in gnus that
I can act upon like the other nnir backends. A search through the (gnus-)
manual didn't turn up anything about notmuch as a nnir backend. Is this
just something missing from the manual, or does a nnir notmuch backend
simply not exist?
If there is no notmuch backend, how do you integrate notmuch into to
gnus? Or do you just use it outside gnus?
>
> Test-installing notmuch isn't too onerous (though the initial indexing
> is slow), it keeps all its business in one directory that you can nuke
> if you don't like it. It also ships with all the necessary elisp files.
> It's also under very active (borderline obsessive) development.
>
An active project certainly is another nice point. All the other
alternatives seem rather inactive to me. (Well, except mu)
>
> The notmuch developers paid me nothing for this message :)
>
Well, even if they did, I am glad for every input I can get :)
>
> Eric
Regards,
--
Alexander Baier
next prev parent reply other threads:[~2013-11-25 14:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 11:50 Alexander Baier
2013-11-25 2:02 ` Dave Goldberg
2013-11-25 8:52 ` Alexander Baier
2013-11-25 8:58 ` Frank Terbeck
2013-11-25 9:11 ` Alexander Baier
2013-11-25 9:01 ` Eric Abrahamsen
2013-11-25 9:13 ` Alexander Baier
2013-11-25 13:20 ` Eric Abrahamsen
2013-11-25 14:08 ` Alexander Baier [this message]
2013-11-25 15:26 ` Eric Abrahamsen
2013-11-25 15:44 ` Frank Terbeck
2013-11-26 4:06 ` Eric Abrahamsen
2013-11-27 5:16 ` Eric Abrahamsen
2013-11-27 7:34 ` Alexander Baier
2013-11-27 8:10 ` Eric Abrahamsen
2013-11-27 8:22 ` Alexander Baier
2013-11-28 12:02 ` Alexander Baier
2013-11-29 3:41 ` Eric Abrahamsen
2013-11-30 18:56 ` Alexander Baier
2013-11-25 16:11 ` Alexander Baier
2013-11-25 9:28 ` Pedro Silva
2013-11-25 9:44 ` Alexander Baier
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=87d2loa812.fsf@gmail.com \
--to=lexi.baier@gmail.com \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).