From: "Jose A. Ortega Ruiz" <jao@gnu.org>
To: ding@gnus.org
Subject: Re: is it possible to search by list-id?
Date: Thu, 08 Jul 2021 18:59:40 +0100 [thread overview]
Message-ID: <87eec8it4j.fsf@gnus.jao.io> (raw)
In-Reply-To: <87sg0oj38s.fsf@gnus.jao.io>
On Thu, Jul 08 2021, Jose A. Ortega Ruiz wrote:
> On Thu, Jul 08 2021, Eric S Fraga wrote:
>
>> On Thursday, 8 Jul 2021 at 02:28, Jose A. Ortega Ruiz wrote:
>>> in the new gnus search, we're told in the docs that 'Supported keys
>>> include all the usual mail headers: “from”, “subject”, “cc”, etc', but,
>>> if i'm not mistaken, that "etc" does not include List-id, does it?
>>
>> Doesn't seem to. Would be nice to have, however.
>
> Right. Moreover, a query including List-ID is not even send to the
> underlying engine (which could perhaps make something of it), because it
> throws an exeception... for instance, this is what i see for the query
> "List-ID: foo" for some nnimap groups (which i have elided):
>
> nnselect-run: gnus-search-run-query on ((search-query-spec (query . "List-ID: foo") (raw)) (search-group-spec ...)) gave error (wrong-type-argument stringp nil)
>
> which looks as if the query parser gets confused.
as a matter of fact, it's a bug very easy to reproduce: just evaluate,
for instance:
(gnus-search-parse-query "foo:bar")
next prev parent reply other threads:[~2021-07-08 18:08 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 [this message]
2021-07-10 1:21 ` Jose A. Ortega Ruiz
2021-07-11 3:21 ` Eric Abrahamsen
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=87eec8it4j.fsf@gnus.jao.io \
--to=jao@gnu.org \
--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).