Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus-search-imap and quoted queries
Date: Tue, 03 May 2022 13:01:37 -0700	[thread overview]
Message-ID: <875ymmmllq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8735htj0ly.fsf@sergiodj.net>

Sergio Durigan Junior <sergiodj@sergiodj.net> writes:

> On Saturday, April 23 2022, Eric Abrahamsen wrote:
>
>> Sergio Durigan Junior <sergiodj@sergiodj.net> writes:
>>
>>> On Tuesday, April 19 2022, I wrote:
>>>
>>>> I have GNUS configured to use a local Dovecot IMAP server (a fairly
>>>> common setup, I think) and I've been trying to get gnus-search-imap
>>>> working.  I set gnus-search-use-parsed-queries to t, by the way.
>>>>
>>>> I noticed that when I specify a quoted query as the search input, the
>>>> results don't reflect what I'd expect.
>>>
>>> FWIW, I finally had some time to look deeper into this and found that
>>> the culprit was the Dovecot FTS plugin I was using (fts-xapian).
>>> It doesn't follow the IMAP RFC strictly and therefore can't/won't do
>>> substring searches.
>>>
>>> I'm now using another Xapian-based plugin called fts-flatcurve which
>>> DTRT.
>>>
>>> Thanks for the help, it's been fun investigating this problem.
>>
>> Hey that's pretty interesting. Looks like I'm using lucene, which seems
>> to work fine. I wonder if it merits a brief mention in the manual that
>> different backends behave differently.
>
> I certainly wouldn't mind seeing this possible idiosyncrasy mentioned in
> the manual.  WDYT about the patch below?
>
> -- 
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> https://sergiodj.net/
>
> From ff85d8b3df751342de6b0071b9c17688086fe744 Mon Sep 17 00:00:00 2001
> From: Sergio Durigan Junior <sergiodj@sergiodj.net>
> Date: Sun, 1 May 2022 01:11:42 -0400
> Subject: [PATCH] Mention different behaviours in IMAP FTS plugins
>
> * doc/misc/gnus.texi (Search Engines): Mention different behaviours in
> IMAP FTS plugins.
> ---
>  doc/misc/gnus.texi | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/doc/misc/gnus.texi b/doc/misc/gnus.texi
> index e51ae7d424d..03330224e09 100644
> --- a/doc/misc/gnus.texi
> +++ b/doc/misc/gnus.texi
> @@ -21727,6 +21727,13 @@ Search Engines
>  to manage updates yourself, though this will likely change in the
>  future.
>  
> +If you use the IMAP search engine you may want to configure your IMAP
> +server to provide Full Text Search (FTS) functionality, which greatly
> +improves the performance and results.  Beware though that some FTS
> +backends may not implement text search as described by RFC 3501, which
> +states that substring search should be performed.  This difference in
> +behaviour can ultimately affect the search results.
> +
>  Lastly, all search engines accept a @code{raw-queries-p} option.  This
>  indicates that engines of this type (or this particular engine) should
>  always use raw queries, never parsed (@pxref{Search Queries}).

Looks good to me! Thanks.



  reply	other threads:[~2022-05-03 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 16:10 Sergio Durigan Junior
2022-04-19 21:30 ` dick
2022-04-19 21:37   ` Sergio Durigan Junior
2022-04-19 22:15     ` dick
2022-04-20 18:49       ` Sergio Durigan Junior
2022-04-20 21:04         ` dick
2022-04-19 22:47     ` Eric Abrahamsen
2022-04-20 19:12       ` Sergio Durigan Junior
2022-04-23  5:23 ` Sergio Durigan Junior
2022-04-23 16:01   ` Eric Abrahamsen
2022-05-01  5:14     ` Sergio Durigan Junior
2022-05-03 20:01       ` Eric Abrahamsen [this message]
2022-05-05  2:06         ` Sergio Durigan Junior

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=875ymmmllq.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).