Re: [O] Inquiry about ical2org
On Friday, 27 May 2016 at 16:06, John Hendy wrote: > Is your original version anywhere handy? I tried searching but don't > seem to find it. I have not made it available since the one on Worg diverged but only because I didn't get around to doing anything about it. Attached is my latest version which I use daily. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3.2-164-g50a182 ical2org.awk Description: Binary data
Re: [O] Inquiry about ical2org
On Fri, May 27, 2016 at 2:50 AM, Eric S Fraga wrote: > On Thursday, 26 May 2016 at 20:04, John Hendy wrote: > > [...] > >> 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 "-- ", the other >> checking for time2 being "". Is that the correct way to go about this? > > Well, I would simply not add the end information as org does not > understand an end date for a repeating item. In other words, for a > repeating item I would simply have the start date including the repeat > directive. > Cool. Commenting has accomplished this for me and I don't get repeating entries anymore. >> Out of curiosity, how *is* the rrend code supposed to be handling >> these? Or what's the use case for building a --? > > I should say that the awk codes have diverged. My own version now > differs significantly from what is on Worg, which is where I assume you > got your copy. I implemented repeating entries differently, it would > seem. Ah, that makes more sense. I was confused about agreeing that an end date wasn't proper but the code having it. Is your original version anywhere handy? I tried searching but don't seem to find it. Thanks, John > > HTH, > eric > > -- > : Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.4-869-gf2c421
Re: [O] Inquiry about ical2org
On Thursday, 26 May 2016 at 20:04, John Hendy wrote: [...] > 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 "-- ", the other > checking for time2 being "". Is that the correct way to go about this? Well, I would simply not add the end information as org does not understand an end date for a repeating item. In other words, for a repeating item I would simply have the start date including the repeat directive. > Out of curiosity, how *is* the rrend code supposed to be handling > these? Or what's the use case for building a --? I should say that the awk codes have diverged. My own version now differs significantly from what is on Worg, which is where I assume you got your copy. I implemented repeating entries differently, it would seem. HTH, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.94.1, Org release_8.3.4-869-gf2c421
Re: [O] Inquiry about ical2org
On 2016-05-26 at 16:00, John Hendy wrote: > On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga wrote: >> On Wednesday, 25 May 2016 at 20:33, John Hendy wrote: >> 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. And a Python version: https://github.com/mankoff/ical2org -k.
Re: [O] Inquiry about ical2org
On Thu, May 26, 2016 at 3:00 PM, John Hendy wrote: > On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga 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=20161114T15Z;INTERVAL=1;BYDAY=2MO > DTSTART;TZID=Central Standard Time:20160613T09 > 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 "-- ", 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 --? 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
Re: [O] Inquiry about ical2org
On Thu, May 26, 2016 at 2:49 AM, Eric S Fraga 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=20161114T15Z;INTERVAL=1;BYDAY=2MO DTSTART;TZID=Central Standard Time:20160613T09 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. > > 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
Re: [O] Inquiry about ical2org
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. 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
[O] Inquiry about ical2org
Greetings, I was looking to get my Outlook calendar into Orgmode to better schedule my work (this way I can see my official meetings in Org already where I do task management). I found ical2org, and implemented it successfully via the "Share calendar" .ics link that Outlook can generate. I have a question on repeated meetings. The default appears to be this format: <2016-05-19 Thu 08:00-09:00 +2w>--<2016-11-17 Thu> I interpret this to be a bi-weekly meeting which runs through 2016-11-17, however agenda puts the meeting on every single day. From reading around, this doesn't appear to be a valid format for accomplishing period recurrences: - http://stackoverflow.com/questions/2464598/org-mode-schedule-weekly-event-for-a-period I just wanted to reach out and see if this is a setup issue or if recursion + a range is not the right way to go about this. If not, my quick fix would see if I can hack the awk script to not include the end date for the range, as deleting that appears to work. That would incorrectly show future appts that may not be real, though. Thanks for any suggestions, John
