From: John Helly <hellyj@ucsd.edu>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: hellyj@ucsd.edu, Emacs-orgmode@gnu.org
Subject: Re: Agenda export to ics file
Date: Fri, 7 Jun 2024 10:02:28 -1000 [thread overview]
Message-ID: <3a64a49a-b424-4bbd-ac3b-b1927acc5bf8@ucsd.edu> (raw)
In-Reply-To: <87r0d894ha.fsf@localhost>
Sure. Thanks for the reply.
1) I put this line at the top of the org file
-*- org-icalendar-use-deadline: t; -*-
and then run the command
M-x icalendar-export-to-ics
This produces an *.ics file but it has only past events (mostly TODOs).
I don't see any sign of upcoming events that I typically have long lead
times on (e.g., -180d). So I'm wondering what I'm doing wrong.
2) When I do the same thing on a different machine, I get a message that
'Symbol’s value as variable is void:
org-agenda-default-appointment-duration'
and no *.ics file is written.
Any help appreciated.
J.
On 6/7/24 05:06, Ihor Radchenko wrote:
> John Helly <hellyj@ucsd.edu> writes:
>
>> I'm a long-time user of emacs, org-mode for about 10 years but cannot
>> figure out how to export DEADLINE events from org-agenda to
>> org-icalendar-export-to-ics.
>>
>> I've found references to setting the
>>
>> org-icalendar-use-deadline
>>
>> variable but haven't yet found the successful incantation to do that.
> May you showcase what exactly you tried?
>
--
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660
next prev parent reply other threads:[~2024-06-07 22:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 22:34 Agenda export to ics file John Helly
2024-06-07 15:06 ` Ihor Radchenko
2024-06-07 20:02 ` John Helly [this message]
2024-06-08 19:20 ` Ihor Radchenko
2024-06-08 20:33 ` John Helly
2024-06-08 20:38 ` Ihor Radchenko
2024-06-08 20:44 ` John Helly
2024-06-08 20:52 ` John Helly
2024-06-08 21:39 ` John Helly
2024-06-09 11:52 ` Ihor Radchenko
2024-06-09 20:22 ` John Helly
2024-06-09 20:31 ` John Helly
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=3a64a49a-b424-4bbd-ac3b-b1927acc5bf8@ucsd.edu \
--to=hellyj@ucsd.edu \
--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).