From: sirjofri <sirjofri@sirjofri.de>
To: ori@eigenstate.org
Cc: 9front@9front.org
Subject: Re: [9front] patch: calendar look ahead
Date: Fri, 10 Jul 2020 07:15:19 +0000 (UTC) [thread overview]
Message-ID: <52ce0729-57c7-492e-a5af-a790c8d5d766@sirjofri.de> (raw)
In-Reply-To: <45690E86AA3E52319A5DF0CEE0BCCB1D@eigenstate.org>
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.
next prev parent reply other threads:[~2020-07-10 7:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:19 sirjofri
2020-07-04 10:01 ` [9front] " sirjofri
2020-07-04 11:05 ` hiro
2020-07-04 14:25 ` Stanley Lieber
2020-07-10 5:31 ` ori
2020-07-10 7:14 ` Steve Simon
2020-07-13 3:58 ` ori
2020-07-10 7:15 ` sirjofri [this message]
2020-07-10 7:20 ` Steve Simon
2020-07-10 9:40 ` [9front] ical calendar (was: calendar look ahead) sirjofri
2020-07-21 4:19 ` [9front] patch: calendar look ahead ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52ce0729-57c7-492e-a5af-a790c8d5d766@sirjofri.de \
--to=sirjofri@sirjofri.de \
--cc=9front@9front.org \
--cc=ori@eigenstate.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.
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 NNTP newsgroup(s).