From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] patch: calendar look ahead
Date: Fri, 10 Jul 2020 08:20:29 +0100 [thread overview]
Message-ID: <07A2B29A-6931-413C-93E1-7A7235E4A434@quintile.net> (raw)
In-Reply-To: <45690E86AA3E52319A5DF0CEE0BCCB1D@eigenstate.org>
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.
-Steve
> On 10 Jul 2020, at 7:32 am, ori@eigenstate.org wrote:
>
>
>>
>> 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,)
next prev parent reply other threads:[~2020-07-10 7:20 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
2020-07-10 7:20 ` Steve Simon [this message]
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=07A2B29A-6931-413C-93E1-7A7235E4A434@quintile.net \
--to=steve@quintile.net \
--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).