From: Julien Cubizolles <j.cubizolles@free.fr>
To: info-gnus-english@gnu.org
Subject: Re: gnus-search since: not working for nnimap
Date: Mon, 30 Jan 2023 10:32:09 +0100 [thread overview]
Message-ID: <87a6201i7a.fsf@free.fr> (raw)
In-Reply-To: <87ilgo1odr.fsf@free.fr>
Julien Cubizolles <j.cubizolles@free.fr> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> We'll have to get closer to the IMAP server, then.
Actually we don't. I didn't pay enough attention to the results of the
previous test you suggested:
--8<---------------cut here---------------start------------->8---
(gnus-search-transform
(make-instance 'gnus-search-imap)
(gnus-search-parse-query "since:1y")) -> "SINCE 28-Jan-2022"
--8<---------------cut here---------------end--------------->8---
returns
--8<---------------cut here---------------start------------->8---
"SINCE 30-janv.-2022"
--8<---------------cut here---------------end--------------->8---
but it should be
--8<---------------cut here---------------start------------->8---
"SINCE 30-jan-2022"
--8<---------------cut here---------------end--------------->8---
'gnus-search-transform seems to be at fault here. It uses
'(format-time-string "%e-%b-%Y") where %b returns the "locale’s
abbreviated month name" when imap commands expects the english abbreviated
month name.
--
Julien Cubizolles
next prev parent reply other threads:[~2023-01-30 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 17:33 Eric Abrahamsen
2023-01-30 7:18 ` Julien Cubizolles
2023-01-30 9:32 ` Julien Cubizolles [this message]
2023-01-30 10:36 ` Julien Cubizolles
2023-01-30 17:41 ` Eric Abrahamsen
2023-02-01 23:05 ` Björn Bidar
-- strict thread matches above, loose matches on Subject: below --
2023-01-28 12:22 Julien Cubizolles
2023-01-28 18:20 ` Eric Abrahamsen
2023-01-29 8:59 ` Julien Cubizolles
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=87a6201i7a.fsf@free.fr \
--to=j.cubizolles@free.fr \
--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).