From: Guido Van Hoecke <guivho@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Handling Repeating events from google calendar / repeater interval
Date: Mon, 08 Jul 2013 17:55:26 +0200 [thread overview]
Message-ID: <m21u79xd01.fsf@gmail.com> (raw)
In-Reply-To: <85k3l1nljo.fsf@damtp.cam.ac.uk> (Stephen Eglen's message of "Mon, 08 Jul 2013 16:00:59 +0100")
Hu Stephen,
Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk> writes:
> 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.
Correct me if I am wrong, but I'm afraid that pure AWK does not provide
date computation support. That's why I did not implement this.
So I would definitely vote to extend the repeater syntax with a count.
>
> 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"
I assume that your initial example RRULE would require either "...4+1d>"
or "+1d:4"
> 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.
+1
Guido
--
We're constantly being bombarded by insulting and humiliating music, which
people are making for you the way they make those Wonder Bread products.
Just as food can be bad for your system, music can be bad for your spirtual
and emotional feelings. It might taste good or clever, but in the long run,
it's not going to do anything for you.
-- Bob Dylan, "LA Times", September 5, 1984
next prev parent reply other threads:[~2013-07-08 15:55 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 [this message]
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
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=m21u79xd01.fsf@gmail.com \
--to=guivho@gmail.com \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--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).