Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus-search configuration example for notmuch
Date: Tue, 22 Mar 2022 08:11:08 -0700	[thread overview]
Message-ID: <87o81yja43.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a6di2yim.fsf@free.fr>

Julien Cubizolles <j.cubizolles@free.fr> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Julien Cubizolles <j.cubizolles@free.fr> writes:
>>
>>> I can't get gnus-search to use notmuch as its search engine for a
>>> maildir synced by offlineimap. Every search with G-G returns 
>>
>> Hi!
>>
>> It's not possible to use notmuch to index an nnimap server. notmuch
>> returns its search results as filenames, and nnimap needs its search
>> results as message ids. 
>
> Thank you, it all makes sense now. Maybe that's also why it doesn't work
> on nnml and nndraft either.
>
> What backend can you use gnus-search-notmuch with then ? And what search
> engines should you use with nnml and nndraft ? Am I right in assuming
> that with the right gnus-search-engines set up gnus-search could search
> through all backends and return the matching messages in a single
> nnselect group ?

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.

And yes, the whole point of gnus-search and nnselect is that you can
search any number of groups and servers, using a single search query and
getting the results in a single group.



  parent reply	other threads:[~2022-03-22 15:11 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 [this message]
2022-03-22 20:22       ` Dan Christensen
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=87o81yja43.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).