From: Eli Zaretskii <eliz@gnu.org>
To: Erwan Hingant <erwan.hingant@mailo.com>, Ulf Jasper <ulf.jasper@web.de>
Cc: rwn@mailo.com, eggert@cs.ucla.edu, 69894@debbugs.gnu.org
Subject: bug#69894: 29.1; Icalendar export conflict with calendar iso date
Date: Sat, 06 Apr 2024 12:58:54 +0300 [thread overview]
Message-ID: <86ttke3j8h.fsf@gnu.org> (raw)
In-Reply-To: <86r0fu2fiq.fsf@mailo.com> (message from Erwan Hingant on Thu, 28 Mar 2024 22:49:33 +0100)
> From: Erwan Hingant <erwan.hingant@mailo.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, RwN <rwn@mailo.com>,
> 69894@debbugs.gnu.org
> Date: Thu, 28 Mar 2024 22:49:33 +0100
>
> Sorry I cannot help much because I am not an expert in
> regexp.... I just find a patch which work for me. The 0? is not in
> the match, the function assume a good structure of the diary file
> so 2024 099 03 will match 2024 99 3 if I am right? What I am
> concern is considering - instead of space likewise the default ISO
> format used .
Can you tell how you arrived at a date such as "2024-03-19" in the
diary file? Did you per chance write it by hand or something? If any
of the diary commands produce such dates, can you show a recipe for
reproducing this?
AFAIU, what icalendar--datestring-to-isodate accepts as DATESTRING is
a diary-style date, and the ISO format of diary-style dates doesn't
allow dashes. So I 'm curious as to how those dashes ended up in your
diary file.
Ulf, any comments about this?
next prev parent reply other threads:[~2024-04-06 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 1:56 bug#69894: 29.1; Icalendar export conflict with calendar iso date RwN via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 9:53 ` Eli Zaretskii
2024-03-28 21:26 ` Paul Eggert
2024-03-28 21:49 ` Erwan Hingant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 9:58 ` Eli Zaretskii [this message]
2024-04-06 10:34 ` Erwan Hingant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-08 5:50 ` Ulf Jasper via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 7:54 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ttke3j8h.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69894@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=erwan.hingant@mailo.com \
--cc=rwn@mailo.com \
--cc=ulf.jasper@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).