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: gnus-search since: not working for nnimap
Date: Sat, 28 Jan 2023 10:20:13 -0800	[thread overview]
Message-ID: <87h6wawmg2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87o7qi26ja.fsf@free.fr>

Julien Cubizolles <j.cubizolles@free.fr> writes:

> I've gnus-search configured to use gnus-search-imap for a nnimap
> method. G G (gnus-group-read-ephemeral-search-group) doesn't return any
> result when using a query like "since:1y" on a nnimap group whereas:
>
> + the same query works in a nnml group
> + a query like "from:user" returns many results in this time range on
>   the same nnimap group.
>
> Isn't "since:1y" a valid query for nnimap ?

It should be!

> The nnimap group is managed by a local dovecot server. Does it
> matter ?

No, I don't think so. I tried it on one of my own nnimap servers, backed
by local dovecot, and it returned several thousand messages.

You can play with the bits and pieces to see where things might be going
wrong:

(gnus-search-query-parse-date "1y") -> (28 1 2022)
(gnus-search-parse-query "since:1y") - > ((since 28 1 2022))

So far so good.

(gnus-search-transform
 (make-instance 'gnus-search-imap)
 (gnus-search-parse-query "since:1y")) -> "SINCE 28-Jan-2022"

Still looking correct (right?).

Try doing "C-u G G" on an nnimap group to shut off gnus-search parsing,
and enter "SINCE 28-Jan-2022" as the search string. Does that return
anything?

Eric



  reply	other threads:[~2023-01-28 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-28 12:22 Julien Cubizolles
2023-01-28 18:20 ` Eric Abrahamsen [this message]
2023-01-29  8:59   ` Julien Cubizolles
2023-01-29 17:33 Eric Abrahamsen
2023-01-30  7:18 ` Julien Cubizolles
2023-01-30  9:32   ` Julien Cubizolles
2023-01-30 10:36     ` Julien Cubizolles
2023-01-30 17:41       ` Eric Abrahamsen
2023-02-01 23:05         ` Björn Bidar

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=87h6wawmg2.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).