emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Sun, 9 Jun 2024 10:31:16 -1000	[thread overview]
Message-ID: <043a4836-0c4d-4b3f-9e8f-f4083715f6e3@ucsd.edu> (raw)
In-Reply-To: <87h6e22uzv.fsf@localhost>

Aha.  I stumbled on the C-hi command and was able to see the current 
setting for the variable and its valid values.

I set the value to 't' and now it seems to do what I want.

Mahalo nui for your excellent help and patience.  I never would have 
discovered this in any reasonable amount of time.

J.

On 6/9/24 01:52, Ihor Radchenko wrote:
> John Helly <hellyj@ucsd.edu> writes:
>
>> So, even this MWE, the export to *.ics does not work as expected. The
>> test.ics file has no events when
>>
>> M-x org-icalendar-export-to-ics
>>
>> is invoked.
>> =========================  Contents of test.org listed below
>> =================
>> -*- org-icalendar-use-deadline: (todo-due);  -*-
>> ...
>> ** TODO This is an event with a Deadline
>> DEADLINE: <2024-06-20 Thu -30d>
> Todo headings are not exported to icalendar by default.
> See `org-icalendar-include-todo'.
>

-- 
John Helly / San Diego Supercomputer Center / Scripps Institution of Oceanography
https://www.sdsc.edu/~hellyj / 808 205 9882 / 760 8408660



      parent reply	other threads:[~2024-06-09 20:32 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
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 [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

  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=043a4836-0c4d-4b3f-9e8f-f4083715f6e3@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).