From: Stefan Kangas <stefankangas@gmail.com>
To: Ulf Jasper <ulf.jasper@web.de>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
56241@debbugs.gnu.org, hokomo <hokomo@airmail.cc>
Subject: bug#56241: [PATCH] icalendar doesn't correctly process arbitrary diary sexp entries
Date: Fri, 11 Nov 2022 05:38:52 -0800 [thread overview]
Message-ID: <CADwFkm=5GRK19a2=9xU1x1tu5-Hrxt7av_DMwLGjQiitgkEX1A@mail.gmail.com> (raw)
In-Reply-To: <8735eq5qee.fsf@panama> (Ulf Jasper's message of "Sun, 24 Jul 2022 20:14:49 +0200")
Ulf Jasper <ulf.jasper@web.de> writes:
> Am 28.06.2022 um 13:21 (+0200) schrieb Lars Ingebrigtsen:
>> hokomo <hokomo@airmail.cc> writes:
>>
>>> Yep, you can use the same testing script and just replace the last
>>> expression with:
>>>
>>> (let ((icalendar-export-sexp-enumeration-days 0))
>>> (test-diary-sexp "%%(diary-float 7 0 1) First Sunday in July 1")
>>> (test-diary-sexp "%%(my-float 7 0 1) First Sunday in July 2"))
>>>
>>> which should give you the error I mentioned.
>>
>> Right; I can reproduce that problem. I've added Ulf to the CCs; perhaps
>> he has some comments.
>
> Sorry for the late reply. Thanks for the bug report, the patch and for
> analysing the problems. I'll try to have a look at the icalendar code
> the next days (or so).
That was 15 weeks ago, so here's a friendly ping.
next prev parent reply other threads:[~2022-11-11 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 18:36 bug#56241: [PATCH] icalendar doesn't correctly process arbitrary diary sexp entries hokomo
2022-06-27 8:04 ` Lars Ingebrigtsen
2022-06-27 9:42 ` hokomo
2022-06-28 11:21 ` Lars Ingebrigtsen
2022-07-06 18:58 ` hokomo
2022-07-07 8:08 ` Lars Ingebrigtsen
2022-07-24 18:14 ` Ulf Jasper
2022-11-11 13:38 ` Stefan Kangas [this message]
2022-11-23 20:24 ` Ulf Jasper
2022-11-24 18:07 ` Ulf Jasper
2023-07-04 10:29 ` Brendan O'Dea
2023-07-04 14:20 ` Mattias Engdegård
2023-07-07 13:15 ` Mattias Engdegård
2024-01-28 17:09 ` Jeremy Harrison via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkm=5GRK19a2=9xU1x1tu5-Hrxt7av_DMwLGjQiitgkEX1A@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=56241@debbugs.gnu.org \
--cc=hokomo@airmail.cc \
--cc=larsi@gnus.org \
--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).