From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: rey-coyrehourcq <sebastien.rey-coyrehourcq@univ-rouen.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Strange interaction between ID block property, org-schedule and ical/ics export backend
Date: Mon, 2 Sep 2019 15:21:06 +0000 [thread overview]
Message-ID: <87imqa7mhq.fsf@ucl.ac.uk> (raw)
In-Reply-To: <2f0c31ea8a7aaafe83d0a05657bbab0fa4b3b4ae.camel@univ-rouen.fr> (rey-coyrehourcq's message of "Mon, 02 Sep 2019 10:34:39 +0200")
On Monday, 2 Sep 2019 at 10:34, rey-coyrehourcq wrote:
> Hi,
> Sorry, i make a typo in the previous mail, i use the "org-icalendar-export-to-
> ics" method and not the org-caldav method...
Ah, okay.
I should say that I only export appointments (i.e. active time stamps)
to ics so it could be that the export doesn't understand
scheduled/deadline items.
Have you looked at the info manual for org icalendar export? It does
mention a couple of variables that may affect what you are getting:
,----[ C-h v org-icalendar-use-deadline RET ]
| org-icalendar-use-deadline is a variable defined in ‘ox-icalendar.el’.
| Its value is (event-if-not-todo todo-due)
|
| Documentation:
| Contexts where iCalendar export should use a deadline time stamp.
|
| This is a list with possibly several symbols in it. Valid symbols are:
|
| ‘event-if-todo’ Deadlines in TODO entries become calendar events.
| ‘event-if-not-todo’ Deadlines in non-TODO entries become calendar events.
| ‘todo-due’ Use deadlines in TODO entries as due-dates.
|
| You can customize this variable.
`----
,----[ C-h v org-icalendar-use-scheduled RET ]
| org-icalendar-use-scheduled is a variable defined in ‘ox-icalendar.el’.
| Its value is (todo-start)
|
| Documentation:
| Contexts where iCalendar export should use a scheduling time stamp.
|
| This is a list with possibly several symbols in it. Valid symbols are:
|
| ‘event-if-todo’ Scheduling time stamps in TODO entries become an event.
| ‘event-if-not-todo’ Scheduling time stamps in non-TODO entries become an event.
| ‘todo-start’ Scheduling time stamps in TODO entries become start date.
| Some calendar applications show TODO entries only after
| that date.
|
| You can customize this variable.
`----
--
: Professor Eric S Fraga, http://www.homepages.ucl.ac.uk/~ucecesf
: PGP/GPG key: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D
: Use plain text email when possible: https://useplaintext.email/
prev parent reply other threads:[~2019-09-02 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 18:42 Strange interaction between ID block property, org-schedule and ical/ics export backend rey-coyrehourcq
2019-09-01 9:29 ` Fraga, Eric
2019-09-02 8:34 ` rey-coyrehourcq
2019-09-02 15:21 ` Fraga, Eric [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=87imqa7mhq.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=sebastien.rey-coyrehourcq@univ-rouen.fr \
/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).