From: Carsten Dominik <dominik@science.uva.nl>
To: Harri Kiiskinen <harri.kiiskinen@utu.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inheritance of LOCATION when exporting ICal (Was: Re: Bug in org-export-icalendar)
Date: Fri, 14 Nov 2008 08:02:00 +0100 [thread overview]
Message-ID: <96502767-5F5B-45BE-AC76-C69CADC11678@uva.nl> (raw)
In-Reply-To: <20081113.164113.208089520.harri.kiiskinen@utu.fi>
Hi Harri,
On Nov 13, 2008, at 3:41 PM, Harri Kiiskinen wrote:
> From: Carsten Dominik <dominik@science.uva.nl>
> Subject: Re: [Orgmode] Bug in org-export-icalendar
> Date: Tue, 11 Nov 2008 17:34:20 +0100
>
>> yes, only times in time stamps will be used in iCalendar export.
>> Times in the headline
>> are too unpredictable. The agenda uses them as a service because
>> nothing really bad can happen. But if you want consistency across
>> applications, you should define times in a consistent way, i.e. in
>> the stamp.
>
> Ok, explanation quite satisfactory. Second wish:
>
> When exporting to icalendar, would it be possible to make the property
> LOCATION to respect the setting in org-use-property-inheritance? I
> like to group seminars under one heading, so I could just set the
> LOCATION property there, and still get it exported to the .ics file
> for each of the sub-headings.
>
> If I understand correctly, the place to change is in org-exp.el, lines
> 4336 and 4458: (org-entry-get nil "LOCATION") from nil to 'selective'
> or something.
almost correct,
(org-entry-get nil "LOCATION" 'selective)
would be the right thing to do. Why don't you try locally
and let us know how it works? One problem is that if you have
large file with N entries, using property inheritance will
eventually make the time required for export scale as N^2,
because for each matching entry, Org will have to scan back
to top-level to find if it should inherit. On could use a
different implementation to make sure that is scales as N, but
the current algorithm does not.
> Perhaps the selective inheritance could be allowed for DEADLINE
> and SCHEDULED, too? I could imagine using this, too.
Same problem as above, and I am no sure if it would break anything.
Maybe maybe not.
- Carsten
>
>
> Best,
>
> Harri K
prev parent reply other threads:[~2008-11-14 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 13:17 Bug in org-export-icalendar Harri Kiiskinen
2008-11-11 16:34 ` Carsten Dominik
2008-11-13 14:41 ` Inheritance of LOCATION when exporting ICal (Was: Re: Bug in org-export-icalendar) Harri Kiiskinen
2008-11-14 7:02 ` Carsten Dominik [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=96502767-5F5B-45BE-AC76-C69CADC11678@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=harri.kiiskinen@utu.fi \
/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).