From: Marcus Zibrowius <marcus.zibrowius@posteo.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-anniversary dates not exported to iCalendar [9.4.6 (9.4.6-3-g37f69b-elpaplus @ /home/marcus/.emacs.d/elpa/org-plus-contrib-20210531/)]
Date: Sun, 23 Jul 2023 20:25:46 +0000 [thread overview]
Message-ID: <306bd343bb8b1b44db1097f3f78f5dcbcff4177a.camel@posteo.net> (raw)
In-Reply-To: <874jlxmnmk.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
> This is because Emacs diary only looks
> `icalendar-export-sexp-enumeration-days' days ahead from now when
> exporting non-standard diary sexps. By default, it is 2 weeks.
> So, you would see the anniversary in icalendar if it were 2 weeks from
> now.
>
> You can increase `icalendar-export-sexp-enumeration-days' to get the
> anniversary occurrences exported up to that number of days ahead.
The variable `icalendar-export-sexp-enumeration-days` is indeed set to 14. However, even entries of the form
* Test 1
%%(org-anniversary 2023 07 22) Test1
* Test 2
%%(org-anniversary 2023 07 24) Test2
do not get exported today (2023 07 23).
> Also, `org-anniversary' does not support %d. AFAIK, it is only working
> for built-in sexp types, which are handled specially.
%d works perfectly in the agenda view.
Marcus
[-- Attachment #2: Type: text/html, Size: 997 bytes --]
next prev parent reply other threads:[~2023-07-23 20:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 12:54 Bug: org-anniversary dates not exported to iCalendar [9.4.6 (9.4.6-3-g37f69b-elpaplus @ /home/marcus/.emacs.d/elpa/org-plus-contrib-20210531/)] Marcus Zibrowius
2023-07-21 12:53 ` Ihor Radchenko
2023-07-23 20:25 ` Marcus Zibrowius [this message]
2023-07-24 7:13 ` Ihor Radchenko
2023-07-24 10:58 ` Marcus Zibrowius
2023-07-24 11:05 ` Ihor Radchenko
2023-07-24 20:28 ` Marcus Zibrowius
2023-07-25 7:05 ` Ihor Radchenko
2023-08-21 7:28 ` Marcus Zibrowius
2023-07-25 11:23 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=306bd343bb8b1b44db1097f3f78f5dcbcff4177a.camel@posteo.net \
--to=marcus.zibrowius@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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/org-mode.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).