From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mimir.eigenstate.org ([206.124.132.107]) by ewsd; Fri Jul 10 01:31:47 EDT 2020
Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 7296628c (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO);
	Thu, 9 Jul 2020 22:31:37 -0700 (PDT)
Message-ID: <45690E86AA3E52319A5DF0CEE0BCCB1D@eigenstate.org>
To: sirjofri@sirjofri.de, 9front@9front.org
Subject: Re: [9front] patch: calendar look ahead
Date: Thu, 9 Jul 2020 22:31:36 -0700
From: ori@eigenstate.org
In-Reply-To: <CAE6D94CC682B014E17F124ED2BA22D9@pizarro.uberspace.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: content-addressed basic blockchain-scale scripting database 

> Hello again,
> 
> I totally forgot to include some more details. I had to send that mail like 3 times because of my mail configuration. Also it seems like 9front ML doesn't accept gmail plain text messages sent with other addresses anymore?
> 
> What is the intended behavior of calendar(1) -p days? Is the attached patch an improvement for calendar(1)?
> 
> These are the questions I wanted to open the disussion with.
> 
> Thank you
> 
> sirjofri

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,)