From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Subject: Handling Repeating events from google calendar / repeater interval
Date: Mon, 08 Jul 2013 16:00:59 +0100
Message-ID: <85k3l1nljo.fsf@damtp.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46874)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <S.J.Eglen@damtp.cam.ac.uk>) id 1UwCwX-0004tW-6Y
	for emacs-orgmode@gnu.org; Mon, 08 Jul 2013 11:01:34 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <S.J.Eglen@damtp.cam.ac.uk>) id 1UwCwU-0002SN-9y
	for emacs-orgmode@gnu.org; Mon, 08 Jul 2013 11:01:33 -0400
Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]:39363)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <S.J.Eglen@damtp.cam.ac.uk>) id 1UwCwU-0002SD-5R
	for emacs-orgmode@gnu.org; Mon, 08 Jul 2013 11:01:30 -0400
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org
Cc: guivho@gmail.com

I'm experimenting using ical2org.sh to import google calendars.  One
limitation, as noted in the header is:

# - does process RRULE recurring events, but ignores COUNT specifiers

so if you have a repeating event in google (e.g. every day for four
week), the ics file has:

RRULE:FREQ=DAILY;COUNT=4

The script will take the first day of the event, but not the remaining
three days.  I think this could be solved in a couple of ways:

1. create four events, moving the date by one each time.

2. extending the syntax of timestamps so that something like:

          * Pick up Sam at school
            <2007-05-16 Wed 12:30 3+1w>

means repeat this event 3 times (rather than indefinitely).  Or "+1w:3"
or something similar, I don't mind the syntax as long as it doesn't
break other parts of timestamps.

Has extending the syntax of the repeater interval been considered to
allow finite number of repeats?  I can offer to code something up for
consideration if this sounds sensible.

Thanks, Stephen