Gnus development mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: gnus-search-imap and quoted queries
Date: Wed, 20 Apr 2022 15:12:20 -0400	[thread overview]
Message-ID: <87v8v3bmcr.fsf@sergiodj.net> (raw)
In-Reply-To: <878rs0667r.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 19 Apr 2022 15:47:36 -0700")

On Tuesday, April 19 2022, Eric Abrahamsen wrote:

> Sergio Durigan Junior <sergiodj@sergiodj.net> writes:
>
>> On Tuesday, April 19 2022, dick wrote:
>>
>>> C-u G G from "Debian FTP Masters"
>>
>> Nothing changed.
>>
>>> The C-u says:
>>> "I'm using Dovecot's query syntax, not Gnus's, so don't mess with it."
>>
>> I'm aware of what C-u does in this case, but IIUC the new gnus-search
>> backend should translate my query into Dovecot's parlance if
>> gnus-search-use-parsed-queries if t, which it is.  Or am I
>> misunderstanding something?
>
> It's possible that something has gone wrong with the handling of the
> quotes. An easy way to tell what's Gnus is looking at is to run:
>
> (let* ((q "from:\"Debian FTP Masters\"")
>        (parsed (gnus-search-parse-query q))
>        (engine (make-instance 'gnus-search-imap :literal-plus t)))
>   (gnus-search-transform engine parsed))
>
> "FROM {20+}
> \"Debian FTP Masters\""
>
> I set :literal-plus because I think that's Dovecot's config out of the
> box. You can also replace the ad-hoc engine there with your actual
> engine, by finding it in `gnus-search-engine-instance-alist'.
>
> If the results look normal to you, the method to edebug is probably
> `gnus-search-imap-search-command'.

Thanks, Eric.

As I wrote in my reply to dick, it seems to me that the query is
correct.  At least I was able to execute it via "doveadm search" and
produce the same results as I see on GNUS.  I'm thinking that the
problem is with how Dovecot interprets the query (and how it doesn't
seem to be searching for the exact terms, even though they are quoted).

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


  reply	other threads:[~2022-04-20 19:12 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 [this message]
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
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=87v8v3bmcr.fsf@sergiodj.net \
    --to=sergiodj@sergiodj.net \
    --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).