From: Sean Whitton <spwhitton@arizona.edu>
To: Andrew Cohen <cohen@bu.edu>
Cc: 62451-close@debbugs.gnu.org
Subject: bug#62451: 29.0.60; nnselect-request-threads assumes gnus-search-use-parsed-queries
Date: Sun, 26 Mar 2023 11:05:54 -0700 [thread overview]
Message-ID: <87ilenie0t.fsf@athena.silentflame.com> (raw)
In-Reply-To: <87355stlhc.fsf@ust.hk> (Andrew Cohen's message of "Sun, 26 Mar 2023 08:17:03 +0800")
Hello,
On Sun 26 Mar 2023 at 08:17AM +08, Andrew Cohen wrote:
>>>>>> "SW" == Sean Whitton <spwhitton@spwhitton.name> writes:
>
> SW> X-debbugs-cc: cohen@bu.edu nnselect-request-threads generates a
> SW> query in Gnus's generic search language and expects
> SW> gnus-search-prepare-query to convert it to a raw query. But if
> SW> gnus-search-use-parsed-queries is nil, as it is by default, then
> SW> this doesn't happen, and the search engine receives a query it
> SW> can't understand. For example, notmuch receives a query like
> SW> "id:<foo> or id:<bar>" when it should receive "id:foo or
> SW> id:bar".
>
> SW> This breaks the gnus-summary-refer-thread command.
>
> SW> One way to fix it is to add a binding
> SW> (gnus-search-use-parsed-queries t) to the let* form in which the
> SW> call to gnus-search-run-query is made.
>
>
> This has been in my tree for ages but I never pushed it (it is part of
> larger changes to thread referral/retrieval). Its worth pushing by
> itself and I'll try to do that.
>
> Sorry for the delay.
Thank you for installing the change. I noticed that you didn't add the
bug number to the commit message -- it would be good if you could do
that next time.
Closing the bug.
--
Sean Whitton
prev parent reply other threads:[~2023-03-26 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 23:16 bug#62451: 29.0.60; nnselect-request-threads assumes gnus-search-use-parsed-queries Sean Whitton
2023-03-26 0:17 ` Andrew Cohen
2023-03-26 18:05 ` Sean Whitton [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=87ilenie0t.fsf@athena.silentflame.com \
--to=spwhitton@arizona.edu \
--cc=62451-close@debbugs.gnu.org \
--cc=cohen@bu.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.