From: John Hendy <jw.hendy@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>, John Hendy <jw.hendy@gmail.com>,
emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inquiry about ical2org
Date: Thu, 26 May 2016 15:04:08 -0500 [thread overview]
Message-ID: <CA+M2ft8u6uzSzPoJSxg7piSTZU+5P9PSdRzDerjzkQJ7W9-ngg@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft_K-DruhE1itd2YjZZaqNTpJ3cGxU_S8MpyRY-fmxwLaA@mail.gmail.com>
On Thu, May 26, 2016 at 3:00 PM, John Hendy <jw.hendy@gmail.com> wrote:
> On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>> On Wednesday, 25 May 2016 at 20:33, John Hendy wrote:
>>> I found ical2org, and implemented it successfully via the "Share
>>
>> Which ical2org is this? If it's the awk script I wrote originally, the
>> repeat handling was written with the assumption that there would be no
>> end date for the repeat as org cannot handled end dates for repeated
>> items.
>
> Whoops -- yes, the awk script. Sorry, now I'm remembering there was a
> ruby version as well.
>
> Here's an example of a recurring meeting I see:
>
> RRULE:FREQ=MONTHLY;UNTIL=20161114T150000Z;INTERVAL=1;BYDAY=2MO
> DTSTART;TZID=Central Standard Time:20160613T090000
> DTEND;TZID=Central Standard Time:20160613T103000
> DTSTAMP:20160526T195005Z
>
> I'm no awk expert, but I think I make out what's going on... the
> #repetition rule section extracts (among others) the freq (monthly)
> and interval (1) to build a repeater (+1m), though and rrend using
> the "until" field.
Bah... sorry about that! Accidental tab right before a space sends away!
Anyway, the point is that the repeater is built if there's any
repetition frequency/interval. You also capture the "until" into
rrend. So, the first date is going to feature a +unit, and this code
adds the end:
else if (rrend != "")
date = date ">--<" rrend
I just commented out both sections that add a "-- <date2>", the other
checking for time2 being "". Is that the correct way to go about this?
If so, no need to update. I'll just leave those commented out.
Out of curiosity, how *is* the rrend code supposed to be handling
these? Or what's the use case for building a <date1 +unit>--<date2>?
Thanks!
John
>>
>> I can try to fix this in the awk script by simply ignoring end dates in
>> such cases. Let me know.
>>
>> --
>> : Eric S Fraga (0xFFFCF67D), Emacs 25.0.93.1, Org release_8.3.4-775-g3308a5
next prev parent reply other threads:[~2016-05-26 20:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <649f280c5d4d4c0b9f100fb9da170cdc@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-26 7:49 ` Inquiry about ical2org Eric S Fraga
2016-05-26 20:00 ` John Hendy
2016-05-26 20:04 ` John Hendy [this message]
2016-05-26 20:24 ` Ken Mankoff
[not found] ` <6aaed23035a1488b92c4c5b556966320@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-27 7:50 ` Eric S Fraga
2016-05-27 16:06 ` John Hendy
[not found] ` <82e201aa4dd34c99b527eb7b1009f062@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-30 12:59 ` Eric S Fraga
2016-05-25 20:33 John Hendy
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=CA+M2ft8u6uzSzPoJSxg7piSTZU+5P9PSdRzDerjzkQJ7W9-ngg@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=e.fraga@ucl.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).