From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: icalendar: exporting times of day specified in heading?
Date: Thu, 28 Jan 2010 19:31:06 +0100 [thread overview]
Message-ID: <D9D53943-F44C-46E5-B19D-3756FFD30C55@gmail.com> (raw)
In-Reply-To: <8420.1264692161@cpc1-cmbg14-2-0-cust6.5-4.cable.virginmedia.com>
On Jan 28, 2010, at 4:22 PM, Stephen Eglen wrote:
> Hi Carsten,
>
>> Hi Stephen,
>>
>> while it might be possible to do what you ask for, I think it is
>> error- prone because people might accidently have something in the
>> headline which looks like a time. I don't mind so much if Org's
>> agenda stumbles over this, but I don't want to produce incorrect
>> icalendar files.
>>
>> Also, this icalendar export function is programmed in a messy way,
>> and
>> I don't see a quick way to fix this.
>>
>> If you can make me a patch, I will take it.
>
> Thanks for this. I did decide to bite the bullet and look into
> this. I
> think I have some working code, modifiying:
> org-agenda-add-entry-to-org-agenda-diary-file
>
> so that it parses out the date at that point, conditional on
> org-agenda-search-headline-for-time being t. In this way, it doesn't
> touch the ical export functions.
>
> I will double check and submit a patch for consideration.
Thanks!
>
> A small note though: along the way, I've sometimes noticed that diary
> entries are included with a level 2 heading rather than a level 4
> heading.
I do not understand this. Included where? How? Can you please
describe this
more extensively?
Thanks
- Carsten
> I haven't been able to track this down, its just noticeable
> when I later browse agenda.org
>
> *** 2010-02-02 Tuesday
> **** 15:00-15:30 check me
> <2010-02-02 Tue>
>
> i.e. that 2nd line is sometimes given two heaings, and is not within
> the
> right level 3 heading. Anything obvious I might want to look at when
> debugging?
>
> Stephen
- Carsten
next prev parent reply other threads:[~2010-01-28 23:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 14:38 icalendar: exporting times of day specified in heading? Stephen Eglen
2010-01-28 14:17 ` Carsten Dominik
2010-01-28 15:22 ` Stephen Eglen
2010-01-28 16:03 ` Eric S Fraga
2010-01-28 18:31 ` Carsten Dominik [this message]
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=D9D53943-F44C-46E5-B19D-3756FFD30C55@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=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.