From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: search for mark over Groups topic not working
Date: Fri, 04 Jun 2021 09:58:25 -0700 [thread overview]
Message-ID: <87sg1xa7ny.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871r9i32qb.fsf@gnus.jao.io>
"Jose A. Ortega Ruiz" <jao@gnu.org> writes:
> so i don't know why it happens, but the problem seems to be in the
> gnus-search-run-search method for imap servers. specifically, this
> snippet translating the query spec to a query string:
>
> (setq q-string
> (gnus-search-make-query-string engine query))
>
>
> - when i run the query mark:! with point at a subtopic, this code in that
> method sets q-string to "FLAGGED", and things work.
> - when i run the query mark:! with point at Gnus, the code above sets
> q-string to "KEYWORD flag" (and, naturally, no results are found).
>
> the reason for that is that, in the first case, query is
>
> ((parsed-query (mark . flag)) (query . mark:!) (raw))
>
> while, in the second case, it is
>
> ((parsed-query (keyword . flag)) (query . mark:!) (raw))
>
> so it seems that the reader of the query, or its translator to a sexp
> down the line, is sensitive to where in the Groups buffer point is.
Whoa, that really shouldn't be the case! Thanks for doing all this
digging, I will have a look this weekend and figure out why it would be
doing that.
next prev parent reply other threads:[~2021-06-04 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 2:31 Jose A. Ortega Ruiz
2021-06-03 18:39 ` Eric Abrahamsen
2021-06-03 19:39 ` Jose A. Ortega Ruiz
2021-06-03 21:27 ` Eric Abrahamsen
2021-06-03 21:36 ` Eric Abrahamsen
2021-06-03 23:41 ` Jose A. Ortega Ruiz
2021-06-03 23:50 ` Jose A. Ortega Ruiz
2021-06-04 0:14 ` Jose A. Ortega Ruiz
2021-06-04 16:58 ` Eric Abrahamsen [this message]
2021-06-04 19:27 ` Eric Abrahamsen
2021-06-30 18:53 ` Jose A. Ortega Ruiz
2021-06-30 19:21 ` 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=87sg1xa7ny.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).