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 03:16:12 EDT 2020 Received: from email.faircode.eu ([178.5.83.171]) by oat; Fri Jul 10 09:14:50 CES 2020 Date: Fri, 10 Jul 2020 07:15:19 +0000 (UTC) From: sirjofri To: ori@eigenstate.org Cc: 9front@9front.org Message-ID: <52ce0729-57c7-492e-a5af-a790c8d5d766@sirjofri.de> In-Reply-To: <45690E86AA3E52319A5DF0CEE0BCCB1D@eigenstate.org> References: <45690E86AA3E52319A5DF0CEE0BCCB1D@eigenstate.org> Subject: Re: [9front] patch: calendar look ahead MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Correlation-ID: <52ce0729-57c7-492e-a5af-a790c8d5d766@sirjofri.de> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: NoSQL-aware replication base cache Hey, 10.07.2020 09:31:57 ori@eigenstate.org: > > The change makes sense to me, but at the moment I don't really use calendar(1), > so I don't have strong opinions. > > (Wishlist item: a utility program to sync between lib/calendar and Google Calendar,) > Google calendar can work with ics calendar files. I started to look into that format and design a "middleware" for simple calendar entries that can output calendar(1) format (and provide its own filesystem). Calendar has not the capabilities of ics, so it will only support a subset, and it might be necessary to add new entries via that filesystem (which provides a proper calendar file and ics file then). Through the power of namespaces you can bind that calendar file over your lib/calendar and the ics file inside a http shared directory (which google calendar can read). I don't think you can add entries via google directly, but an ics import feature is planned.