From: sirjofri <sirjofri@sirjofri.de>
To: Steve Simon <9front@9front.org>
Cc: 9front@9front.org
Subject: Re: [9front] ical calendar (was: calendar look ahead)
Date: Fri, 10 Jul 2020 09:40:04 +0000 (UTC) [thread overview]
Message-ID: <2f3ee7c1-e459-4592-b167-a18d9429ce25@sirjofri.de> (raw)
In-Reply-To: <07A2B29A-6931-413C-93E1-7A7235E4A434@quintile.net>
Hey all,
10.07.2020 11:20:49 Steve Simon <steve@quintile.net>:
> another offering - i added support for recurrent calendar entries if 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 first thursday" dates.
About your ical stuff: I guess we could also start a open source project for 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 (events 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-writeable interface for creating new entries (new/desc, new/start) and a file 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
next prev parent reply other threads:[~2020-07-10 9:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 14:19 patch: calendar look ahead 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
2020-07-10 7:20 ` Steve Simon
2020-07-10 9:40 ` sirjofri [this message]
2020-07-21 4:19 ` 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=2f3ee7c1-e459-4592-b167-a18d9429ce25@sirjofri.de \
--to=sirjofri@sirjofri.de \
--cc=9front@9front.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).