Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: wrong gnus-search in nnml folder
Date: Wed, 01 Feb 2023 10:05:47 -0800	[thread overview]
Message-ID: <87mt5xb6ro.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87wn52wo6c.fsf@gmail.com>

Angel de Vicente <angel.vicente.garrido@gmail.com> writes:

> Hello,
>
> Angel de Vicente <angel.vicente.garrido@gmail.com> writes:
>> oh, indeed it was nil. Changed it and queries like "since:3d" work now
>> beautifully. What I don't get to work is compound queries like since:3d
>> from:alex (they work separetely, but nothing gets returned if I try to
>> combine two queries...
>
> just tried again today. I thought I would have to fire edebug again, but
> I tried quoting the whole query and it works fine.
>
> So, to clarify:
>
> + for simple queries I just type:
>
> Query: since:3d
>
> + for compound queries I need to quote it like:
>
> Query: "from:alex since:3d"
>
> I take it from section 9.3 of the Gnus manual that this is not intended.

No, that's not how it's supposed to work! So here's our query:

(gnus-search-transform
 (make-instance 'gnus-search-mairix)
 (gnus-search-parse-query "from:alex since:3d"))

-> "f:alex d:20230128-"

And you've confirmed that running "mairix f:alex d:20230128-" works
correctly on the command line?

There's not much other processing going on. Mairix is weird about how it
ANDs and ORs search terms -- you can only OR on the same key -- but that
shouldn't be coming into play here.

For the record, you don't really need to be using gnus-search. If you're
happy with mairix's search language, and you don't expect to ever run
searches against both nnml and nnimap backends at the same time, it
probably won't get you much.

Eric



  parent reply	other threads:[~2023-02-01 18:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 11:35 Angel de Vicente
2023-01-30 17:45 ` Eric Abrahamsen
2023-01-30 18:14   ` Angel de Vicente
2023-01-30 18:27     ` Angel de Vicente
2023-01-30 18:46       ` Eric Abrahamsen
2023-01-30 20:54         ` Angel de Vicente
2023-01-30 21:18           ` Angel de Vicente
2023-01-30 22:34             ` Eric Abrahamsen
2023-01-30 23:22               ` Angel de Vicente
2023-01-31 18:31                 ` Angel de Vicente
2023-01-31 18:39                   ` Angel de Vicente
2023-02-01 18:05                   ` Eric Abrahamsen [this message]
2023-02-02  3:15                 ` Fernando de Morais
2023-02-02  6:17                   ` Eric Abrahamsen
2023-02-02 11:44                     ` Angel de Vicente
2023-02-02 12:06                     ` Fernando de Morais

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=87mt5xb6ro.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@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).