From: Carsten Dominik <C.Dominik@uva.nl>
To: Adam Spiers <orgmode@adamspiers.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: iCal export of repeated tasks
Date: Thu, 12 Jun 2008 12:54:04 +0200 [thread overview]
Message-ID: <EDCE1F04-B131-47E8-B43D-6601649DEF60@uva.nl> (raw)
In-Reply-To: <20080612100559.GE19396@atlantic.linksys.moosehall>
On Jun 12, 2008, at 12:05 PM, Adam Spiers wrote:
> On Thu, Jun 12, 2008 at 08:02:48AM +0200, Carsten Dominik wrote:
>> On Jun 10, 2008, at 12:17 PM, Adam Spiers wrote:
>>
>>> Currently, if I have a repeated task such as
>>>
>>> * NEXT [#B] water plants
>>> SCHEDULED: <2008-06-16 Mon 10:30-10:45 .+1w>
>>>
>>> then iCal export includes something like this in the VEVENT:
>>>
>>> RRULE:FREQ=WEEKLY;INTERVAL=1
>>>
>>> For most repeated tasks, this is a perfectly sensible default.
>>> However, for a task of this nature, I only want to see the next
>>> occurrence show up in my calendar client - any more just clutters up
>>> the monthly view. So I would suggest that there should be an option
>>> to control whether the repeated occurrences get exported. Even
>>> better
>>> if you could limit this to only apply to certain types of repeat;
>>> maybe having it only apply to the 'battery charging' type of
>>> renewable
>>> events denoted by '.+' would make a sensible default?
>>
>> I don't think the icalendar format does support repeated entries
>> for a
>> limited time interval, does it?
>
> Quite possibly not - however this need not get in the way of my
> suggestion, which was simply to export the repeated event as a one-off
> where appropriate. Does that make sense?
Not really, to be honest. I am having trouble to envision a good
definitions of when a repeated event is a repeated one and when not.
- Carsten
next prev parent reply other threads:[~2008-06-12 10:54 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 [this message]
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
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=EDCE1F04-B131-47E8-B43D-6601649DEF60@uva.nl \
--to=c.dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@adamspiers.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).