From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from oat.nine.sirjofri.de ([5.45.105.127]) by ewsd; Fri Jul 10 05:40:24 EDT 2020
Received: from email.faircode.eu ([178.5.83.171]) by oat; Fri Jul 10 11:39:34 CES 2020
Date: Fri, 10 Jul 2020 09:40:04 +0000 (UTC)
From: sirjofri <sirjofri@sirjofri.de>
To: Steve Simon <9front@9front.org>
Cc: 9front@9front.org
Message-ID: <2f3ee7c1-e459-4592-b167-a18d9429ce25@sirjofri.de>
In-Reply-To: <07A2B29A-6931-413C-93E1-7A7235E4A434@quintile.net>
References: <45690E86AA3E52319A5DF0CEE0BCCB1D@eigenstate.org> <07A2B29A-6931-413C-93E1-7A7235E4A434@quintile.net>
Subject: Re: [9front] ical calendar (was: calendar look ahead)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Correlation-ID: <2f3ee7c1-e459-4592-b167-a18d9429ce25@sirjofri.de>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: private webscale firewall hosting hypervisor DOM-oriented manager 

Hey all,

10.07.2020 11:20:49 Steve Simon <steve@quintile.net>:
> another offering - i added support for recurrent=C2=A0 calendar entries i=
f the form:
>
> weekly meetings:
> every wed <meeting description>
>
> the same day every month:
> the first wed <meeting description>
>
> happy to share if anyone wants.

9front calendar(1) already has support for weekly events. At least I use it=
 and it works (see man page). I'm not sure about the more complex "every fi=
rst thursday" dates.

About your ical stuff: I guess we could also start a open source project fo=
r that.

I thought about reading and writing a ical database for the user, which is =
the source and then a filesystem with a proper abstraction of the data (eve=
nts as directories, ...). Of course a calendar file for calendar(1), so we =
can use standard plan9 tools as well. The filesystem would provide a user-w=
riteable interface for creating new entries (new/desc, new/start) and a fil=
e for importing new events from an ical file (new.ical).

Iirc ori was improving date functions? I don't know if they are finally in =
main, there were some problems, I think? This might help with timezones and=
 date parsing in general.

sirjofri