From: ori@eigenstate.org
To: sstallion@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] Gmail vs upas
Date: Mon, 2 Dec 2019 15:27:26 -0800 [thread overview]
Message-ID: <823EC81AB1DB4BFEEE9AA1FEC417CF8A@eigenstate.org> (raw)
In-Reply-To: <CAGGHmKH0b6a3SX1gyzaTBFcs20aTeB50C1GWkfw1Ss-EQxq4mQ@mail.gmail.com>
> Looks like that was it - thanks a lot David! IMAP is syncing as we
> speak. It looks like I have my work cut out for me to get things
> updated to 9legacy's latest and greatest.
>
> Cheers,
> Steve
I've put some patches together that made acme Mail a bunch more usable
for me. Mostly around showing read/replied flags. If you want, feel
free to prepare patches for 9legacy, and I'll be more than happy to
give a hand:
https://code.9front.org/hg/plan9front/rev/c6d4c49b1653
https://code.9front.org/hg/plan9front/rev/aca41046f6ee
There are also a couple of upas changes, but our upas in 9front is
based on nupas, and not the one in 9legacy -- still, I was staring at
the imap code in both to understand what was going on, and I think the
approach to not fetching everything should be applicable:
https://code.9front.org/hg/plan9front/rev/99a26b67689a
Unrelatedly, would there be interest in adding the `$split{cmd} syntax
from 9atom to 9legacy? I think it's currently the only reason that
git9 doesn't work out of the box there, and it's very nice syntax.
next prev parent reply other threads:[~2019-12-02 23:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 15:39 Steven Stallion
2019-11-28 15:55 ` [9fans] " Steve Simon
2019-11-28 16:00 ` David du Colombier
2019-11-28 17:13 ` Steven Stallion
2019-11-28 17:37 ` kvik
2019-11-28 17:44 ` Steven Stallion
2019-11-28 18:07 ` kvik
2019-11-28 18:59 ` David du Colombier
2019-11-28 20:28 ` Steven Stallion
2019-12-02 23:27 ` ori [this message]
2019-12-03 10:52 ` Richard Miller
2019-12-04 20:50 ` ori
2019-12-04 23:02 ` Richard Miller
2019-12-03 13:54 ` Anthony Martin
2019-11-28 17:33 ` kvik
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=823EC81AB1DB4BFEEE9AA1FEC417CF8A@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
--cc=sstallion@gmail.com \
/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).