From: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
To: emacs-orgmode@gnu.org
Cc: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Subject: icalendar: exporting times of day specified in heading?
Date: Sat, 16 Jan 2010 14:38:36 +0000 [thread overview]
Message-ID: <15490.1263652716@cpc1-cmbg14-2-0-cust6.5-4.cable.virginmedia.com> (raw)
Hi,
I often use org-agenda-diary-entry to make simple entries into
an agenda.org file. I see that the agenda is clever enough to recognise
if a time range has been typed into the heading. However, this time
range is not exported by the icalendar code.
Here's a simple example, independent of org-agenda-diary-entry, although
in reality, example 2 would be the type of entry I normally make.
if I have a test.org file containing:
----------------------------------------------------------------------
* <2010-01-16 Sat 08:00-08:30> example 1
* <2010-01-16 Sat> example 2 09:00-09:30
----------------------------------------------------------------------
then when I view the agenda I see:
Saturday 16 January 2010
test: 8:00- 8:30 example 1
8:00...... ----------------
test: 9:00- 9:30 example 2
10:00...... ----------------
[There's an extra space before 'example 2', which I'm not sure about.]
So far, so good - the agenda has parsed 09:00-09:30 from the headline.
But now if I make an ics file (e.g. by 'C-c C-e i' in test.org) the
start and end time of the event are not recognised. Here's a relevant
snippet from test.ics:
BEGIN:VCALENDAR
...
DTSTART:20100116T080000
DTEND:20100116T083000
SUMMARY: example 1
CATEGORIES:test
...
DTSTART;VALUE=DATE:20100116
DTEND;VALUE=DATE:20100117
SUMMARY: example 2 09:00-09:30
What I *think* I'd like is that for the 2nd calendar entry is
DTSTART:20100116T0900
DTEND:20100116T0930
Is that sensible/possible? Alternatively, how about
org-agenda-diary-entry parsing the time specification and writing the
date and time within angle brackets?
(org-version)
"Org-mode version 6.33trans (release_6.33f.22.gcb8ce.dirty)"
Thanks, Stephen
next reply other threads:[~2010-01-16 14:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 14:38 Stephen Eglen [this message]
2010-01-28 14:17 ` icalendar: exporting times of day specified in heading? Carsten Dominik
2010-01-28 15:22 ` Stephen Eglen
2010-01-28 16:03 ` Eric S Fraga
2010-01-28 18:31 ` Carsten Dominik
2010-01-29 13:04 ` Eric S Fraga
2010-01-29 13:10 ` Stephen Eglen
2010-02-01 12:41 ` Stephen Eglen
2010-02-01 13:31 ` Carsten Dominik
2010-02-01 13:49 ` Eric S Fraga
2010-02-01 14:00 ` Stephen Eglen
2010-02-01 14:08 ` Stephen Eglen
2010-02-02 13:16 ` Stephen Eglen
2010-02-03 15:25 ` Carsten Dominik
2010-03-17 13:26 ` Matt Lundin
2010-03-17 13:40 ` Stephen Eglen
2010-03-17 15:28 ` Stephen Eglen
2010-03-17 15:55 ` Carsten Dominik
2010-03-17 18:51 ` Stephen Eglen
[not found] ` <0F399028-B7BE-4C90-AEA7-099AC05E9040@tsdye.com>
2010-03-17 20:15 ` Stephen Eglen
2010-03-18 2:17 ` Matthew Lundin
2010-03-18 5:37 ` Carsten Dominik
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=15490.1263652716@cpc1-cmbg14-2-0-cust6.5-4.cable.virginmedia.com \
--to=s.j.eglen@damtp.cam.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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.