From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus-search configuration example for notmuch
Date: Wed, 23 Mar 2022 12:19:12 -0700 [thread overview]
Message-ID: <87cziciij3.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874k3od2j6.fsf@uwo.ca>
Dan Christensen <jdc@uwo.ca> writes:
> On Mar 23, 2022, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>
>> Dan Christensen <jdc@uwo.ca> writes:
>>
>>> 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
>>>
>>> I guess nnfolder is also a special case?
>>
>> I don't think nnfolder is a special case: as long as both the Gnus
>> backend and the search engine deal in absolute file paths, they should
>> be able to talk to one another. If something special needs to be done to
>> translate mairix search results into something that nnfolder can
>> understand, I'd like to know about that and implement it.
>
> With nnfolder, each file contains an entire group's worth of messages.
> So how can it work if mairix provides just a list of full filenames?
It won't! Unless mairix can provide a matching line number, or some
other indication of where in the file the match is, we won't be able to
find the matching message. I can't think of any simple way around the problem.
prev parent reply other threads:[~2022-03-23 19:19 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
2022-03-23 16:37 ` Eric Abrahamsen
2022-03-23 17:03 ` Dan Christensen
2022-03-23 19:19 ` Eric Abrahamsen [this message]
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=87cziciij3.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).