From: Paul R <paul.r.ml@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: iCal export of repeated tasks
Date: Fri, 13 Jun 2008 11:55:19 +0200 [thread overview]
Message-ID: <878wx964mw.fsf@gmail.com> (raw)
In-Reply-To: <20080613092409.GA8066@atlantic.linksys.moosehall> (Adam Spiers's message of "Fri\, 13 Jun 2008 10\:24\:09 +0100")
Hi Adam,
>> It seems to be fine for the program displaying the info to do such
>> filtering - this is what Org does in the agenda.
>
> Unfortunately, since the proposed filtering is per-event, with
> uni-directional export to other clients, the only place it can be done
> is at the source, i.e. within Org. Otherwise some layering of extra
> filtering meta-data per-event would be required for each external
> calendaring client, which would be extremely cumbersome.
Like Dominik, I consider a repeated event as a calendar object on its
own. Such an object has a representation in the iCal format. Org mode
must stick to the correct representation of this object, and it is up
to each calendar tool to display it in a way or an other to the user.
If you consider others tools as broken in this area, and don't feel
like fixing them, you can maybe implement a "go-between" layer that
takes iCal file in input, and outputs the same iCal file with repeated
events changed to dated events, with date set on next occurence.
--
Paul
next prev parent reply other threads:[~2008-06-13 9:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 10:17 iCal export of repeated tasks Adam Spiers
2008-06-12 6:02 ` Carsten Dominik
2008-06-12 10:05 ` Adam Spiers
2008-06-12 10:54 ` Carsten Dominik
2008-06-12 11:47 ` Adam Spiers
2008-06-13 8:18 ` Carsten Dominik
2008-06-13 9:24 ` Adam Spiers
2008-06-13 9:55 ` Paul R [this message]
2008-06-13 12:01 ` Adam Spiers
2008-06-13 12:56 ` Paul R
2008-06-13 14:16 ` Adam Spiers
2008-06-13 10:28 ` Carsten Dominik
2008-06-13 11:48 ` Adam Spiers
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=878wx964mw.fsf@gmail.com \
--to=paul.r.ml@gmail.com \
--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 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).