Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: ding@gnus.org
Subject: Re: is it possible to search by list-id?
Date: Sat, 10 Jul 2021 20:21:44 -0700	[thread overview]
Message-ID: <874kd11qnr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8735sn3qw5.fsf@gnus.jao.io> (Jose A. Ortega Ruiz's message of "Sat, 10 Jul 2021 02:21:30 +0100")

"Jose A. Ortega Ruiz" <jao@gnu.org> writes:

> it seems to be possible to make this word (at least for searches backed
> by dovecot's fts) simply with:
>
>   (add-to-list 'gnus-search-expandable-keys "list-id")
>
> that is makng the error parsing the query go away, and transforming to
> the spec ((list-id . "foo")), which in turn dovecot's IMAP search engine
> seems to like.
>
> not sure if this is intended behaviour, but, as they say,
> se non è vero, è ben trovato! :)

No, this was a misunderstanding about how `completion-all-completions'
works, the queries are definitely meant to pass unknown keywords
straight through to the underlying engine. I've patched this now, and
added new tests to prevent regression. Thanks for pointing it out!

Eric


  reply	other threads:[~2021-07-11  3:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  1:28 Jose A. Ortega Ruiz
2021-07-08 13:15 ` Eric S Fraga
2021-07-08 14:21   ` Jose A. Ortega Ruiz
2021-07-08 17:59     ` Jose A. Ortega Ruiz
2021-07-10  1:21       ` Jose A. Ortega Ruiz
2021-07-11  3:21         ` Eric Abrahamsen [this message]
2021-07-11  7:06           ` Adam Sjøgren
2021-07-11 15:33             ` Eric Abrahamsen
2021-07-11 16:28               ` Adam Sjøgren
2021-07-11 16:42                 ` Eric Abrahamsen
2021-07-11 15:34           ` Jose A. Ortega Ruiz
2021-07-11 16:35             ` 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=874kd11qnr.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=ding@gnus.org \
    --cc=jao@gnu.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).