emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Adam Spiers <orgmode@adamspiers.org>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Re: iCal export of repeated tasks
Date: Fri, 13 Jun 2008 15:16:02 +0100	[thread overview]
Message-ID: <20080613141602.GI26718@atlantic.linksys.moosehall> (raw)
In-Reply-To: <87y7594hp2.fsf@gmail.com> <878wx964mw.fsf@gmail.com>

On Fri, Jun 13, 2008 at 11:55:19AM +0200, Paul R wrote:
> [...] 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.

On Fri, Jun 13, 2008 at 02:56:09PM +0200, Paul R wrote:
> This is a good use-case, and once again, I consider org export should
> provide full information, and later a convert tools should
> degrade/adapt it to the target software or device. Implementing such a
> processing in every calendaring tools would be a massive duplication.
> The "iCal to iCal" converter is the way to go, IMO.

I see your point.  The main disadvantage is that it doesn't work if
you want to apply the filter to the view in the client which
originally generated the iCal from the "master" event data (in our
case, org-mode) - you'd have to export it, pass it through the filter,
then reimport it ...

  parent reply	other threads:[~2008-06-13 14:16 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
2008-06-13 12:01               ` Adam Spiers
2008-06-13 12:56                 ` Paul R
2008-06-13 14:16               ` Adam Spiers [this message]
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=20080613141602.GI26718@atlantic.linksys.moosehall \
    --to=orgmode@adamspiers.org \
    --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).