From: Jeremy Harrison via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "56241@debbugs.gnu.org" <56241@debbugs.gnu.org>
Subject: bug#56241: [PATCH] icalendar doesn't correctly process arbitrary diary sexp entries
Date: Sun, 28 Jan 2024 17:09:52 +0000 [thread overview]
Message-ID: <ELeVwOYlAVv651hpEHfQROY6pUE2AK5ChzuK_d1e8dKaNRThVkTWIP0PfMKqoMu346d3CzsBgY7IdeYSPIKN8KcmChnpqQ7UrweIJPzQw24=@harrisonbundrock.com> (raw)
In-Reply-To: <21bff87f-b8dc-c7bc-41ab-97c7077a0535@airmail.cc>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
Not sure if this helps but I was wondering why exporting '%%(org-anniversary 2020 02 02) blah %d blah' worked but '%%(org-anniversary 2020 03 02) blah %d blah' did not.
Long story short, icalendar-export-sexp-enumeration-days was set to 14 by default. I have changed this to 366 and the export works again.
If relevant, I noticed that one of the tests mentioned above does not set the value explicitly while the others do.
I'm not a programmer so take my observations with due caution!
Jeremy
[-- Attachment #2: Type: text/html, Size: 1343 bytes --]
prev parent reply other threads:[~2024-01-28 17:09 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
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 [this message]
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='ELeVwOYlAVv651hpEHfQROY6pUE2AK5ChzuK_d1e8dKaNRThVkTWIP0PfMKqoMu346d3CzsBgY7IdeYSPIKN8KcmChnpqQ7UrweIJPzQw24=@harrisonbundrock.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=56241@debbugs.gnu.org \
--cc=jeremy@harrisonbundrock.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.