From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: gnus-search configuration example for notmuch
Date: Tue, 22 Mar 2022 16:22:39 -0400 [thread overview]
Message-ID: <87wnglu48g.fsf@uwo.ca> (raw)
In-Reply-To: <87o81yja43.fsf@ericabrahamsen.net>
On Mar 22, 2022, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> To add to what everyone else has said: most of the mail backends (nnml,
> nnmaildir, etc) keep their messages as files on the file system, so any
> search engine that indexes files and gives you full filenames back as
> search results (including notmuch, namazu, mairix) will work with them.
> It's really nnimap that is a special case, as you're not supposed to
> know or care where/how it stores its messages, and instead use the
> client/server interface.
I guess nnfolder is also a special case? My mail is currently split
between nnfolder and nnimap (using dovecot), and my current search
engine is mairix, which can provide its results as a folder full of
files each containing a single message. Right now I use nnmairix to
view my search results, but it is a bit buggy and doesn't have some
features than gnus-search and nnselect seem to have, so I wouldn't
mind switching. But since I'm pretty familiar with the mairix search
syntax, I'd like to keep using mairix. Is this not possible?
Dan
next prev parent reply other threads:[~2022-03-23 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 16:10 Julien Cubizolles
2022-03-21 23:33 ` Eric Abrahamsen
2022-03-22 8:16 ` Julien Cubizolles
2022-03-22 9:58 ` Adam Sjøgren
2022-03-22 10:28 ` Eric S Fraga
2022-03-22 11:31 ` Julien Cubizolles
2022-03-22 15:11 ` Eric Abrahamsen
2022-03-22 20:22 ` Dan Christensen [this message]
2022-03-23 16:37 ` Eric Abrahamsen
2022-03-23 17:03 ` Dan Christensen
2022-03-23 19:19 ` Eric Abrahamsen
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=87wnglu48g.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).