I pushed some conversion code which I am more confident about to the
tz-test branch. If you want to re-test, please do so.
Cheers,
Simon
On 08/08/2013 10:56 PM, Simon Thum wrote:
Stephen,
I now have time to take a look if you send me an example ical.
Cheers,
Simon
On 07/31/2013 11:18 PM
Stephen,
I now have time to take a look if you send me an example ical.
Cheers,
Simon
On 07/31/2013 11:18 PM, Simon Thum wrote:
Yes, probably, but don't count on me in the next 4 days (vacation).
On 07/31/2013 11:08 PM, Stephen Eglen wrote:
On Wed, Jul 31 2013, Simon Thum wrote:
Hi Ste
Yes, probably, but don't count on me in the next 4 days (vacation).
On 07/31/2013 11:08 PM, Stephen Eglen wrote:
On Wed, Jul 31 2013, Simon Thum wrote:
Hi Stephen,
I probably did not express myself well: The [UTC] means the timestamp
was converted from UTC, which is the case. It is probably
Neil Smithline writes:
> On Mon, Jul 8, 2013 at 11:55 AM, Guido Van Hoecke
> wrote:
>
>
>
> Correct me if I am wrong, but I'm afraid that pure AWK does not
> provide date computation support.
Apparently I was not very awake when I wrote that. Awk could be used to
increment dat
On Mon, Jul 8, 2013 at 11:55 AM, Guido Van Hoecke wrote:
>
> 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.
Before defending my prec
Hi Stephen,
I probably did not express myself well: The [UTC] means the timestamp
was converted from UTC, which is the case. It is probably quite
confusing to attach a TZ which is no longer supposed to be the case. I
will probably change that.
Is the org-mode time a correct local time now? I
> sorry the patch was incomplete. The correct one is on a branch I just
> pushed named "tz-test".
>
> For me it works the same but maybe it works for you.
Thanks Simon, but unfortuantely I'm still seeing [UTC].
Stephen
Hi,
sorry the patch was incomplete. The correct one is on a branch I just
pushed named "tz-test".
For me it works the same but maybe it works for you.
Cheers,
Simon
On 07/23/2013 04:42 PM, Stephen Eglen wrote:
Yes, org-mode does not recognize the [UTC], that is just a helper for
exactly
>
> Yes, org-mode does not recognize the [UTC], that is just a helper for
> exactly this case: The ical's timezone is emitted in case it is
> different from your DEFAULT_TZ. For me it worked fine so far.
Thanks.
>res = orgTimeSpan(tstart, tend, repeaterClause)
>
> for
>res = orgTimeSpan
On 07/16/2013 06:02 PM, Stephen Eglen wrote:
It's not exactly answering your question but my little tool
https://github.com/simonthum/ical2org
Dear Simon,
Does your script handle summer time differences? My google calendar
items are importing okay, but they are off by one hour. I've tried
> 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.
okay, it does sound like a lot to ask awk to do.
> So I would definitely vote to extend the repeater syntax with a count.
great.
> I assume that your initial
> It's not exactly answering your question but my little tool
>
> https://github.com/simonthum/ical2org
Thanks, this is a nice workaround, it just worked well on my google
calendar import. Should we add a link to this on
http://orgmode.org/worg/org-tutorials/org-google-sync.html
(how do I edit t
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 proce
Hu Stephen,
Stephen Eglen 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
> we
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
15 matches
Mail list logo
