emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Simon Thum <simon.thum@gmx.de>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: guivho@gmail.com, emacs-orgmode@gnu.org
Subject: Re: Handling Repeating events from google calendar / repeater interval
Date: Tue, 09 Jul 2013 08:38:14 +0200	[thread overview]
Message-ID: <51DBAFD6.1030608@gmx.de> (raw)
In-Reply-To: <85k3l1nljo.fsf@damtp.cam.ac.uk>

It's not exactly answering your question but my little tool

https://github.com/simonthum/ical2org

handles these.

HTH,

Simon

On 07/08/2013 05:00 PM, Stephen Eglen wrote:
> 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
>
>

  parent reply	other threads:[~2013-07-09  6:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 15:00 Handling Repeating events from google calendar / repeater interval Stephen Eglen
2013-07-08 15:55 ` Guido Van Hoecke
2013-07-09  9:08   ` Stephen Eglen
2013-07-31 13:45   ` Neil Smithline
2013-07-31 19:42     ` Guido Van Hoecke
2013-07-09  6:38 ` Simon Thum [this message]
2013-07-09  9:07   ` Stephen Eglen
     [not found]   ` <85ppuisdax.fsf@damtp.cam.ac.uk>
2013-07-21 10:44     ` Simon Thum
2013-07-23 14:42       ` Stephen Eglen
2013-07-28  9:00         ` Simon Thum
2013-07-30 13:06           ` Stephen Eglen
2013-07-31 12:48             ` Simon Thum
     [not found]               ` <m27gg6h1z8.fsf@damtp.cam.ac.uk>
2013-07-31 21:18                 ` Simon Thum
2013-08-08 20:56                   ` Simon Thum
2013-08-09 20:32                     ` Simon Thum

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=51DBAFD6.1030608@gmx.de \
    --to=simon.thum@gmx.de \
    --cc=S.J.Eglen@damtp.cam.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=guivho@gmail.com \
    /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).