GNU bug report logs - #69894
29.1; Icalendar export conflict with calendar iso date

Previous Next

Full log

Message #17 received at 69894 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Erwan Hingant <erwan.hingant <at> mailo.com>, Ulf Jasper <ulf.jasper <at> web.de>
Cc: rwn <at> mailo.com, eggert <at> cs.ucla.edu, 69894 <at> debbugs.gnu.org
Subject: Re: bug#69894: 29.1; Icalendar export conflict with calendar iso date
Date: Sat, 06 Apr 2024 12:58:54 +0300

> From: Erwan Hingant <erwan.hingant <at> mailo.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,   RwN <rwn <at> mailo.com>,
>    69894 <at> 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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.