From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: wrong gnus-search in nnml folder
Date: Mon, 30 Jan 2023 10:46:59 -0800 [thread overview]
Message-ID: <87k013oo64.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87o7qf6fp6.fsf@gmail.com>
Angel de Vicente <angel.vicente.garrido@gmail.com> writes:
>>> You haven't said what search engine you're using, but if it's notmuch:
>>
>> it is ages since I configured this, but I'm not using notmuch, it is
>> just whatever stock method comes with Gnus, *I think*
>
> should be mairix.
>
> my gnus-search-default-engines variable' value is:
>
> ,----
> | ((nnimap . gnus-search-imap)
> | (nnml . gnus-search-mairix))
> `----
So that's:
(gnus-search-transform
(make-instance 'gnus-search-mairix)
(gnus-search-parse-query "since:3d")) -> "d:20230127-"
As I read the spec, that's the correct format (actually, mairix could
also handle the "3d" directly, but there's currently no option to pass
the unparsed search string through). Can you check on the command line,
outside of Gnus, and confirm that you see the correct messages returned?
You can also edebug `gnus-search-run-search' for the
`gnus-search-indexed' engine (gnus-search.el:1394 in master), and see
if anything funky is happening in there.
next prev parent reply other threads:[~2023-01-30 18:47 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 [this message]
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
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=87k013oo64.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).