From: Lucio De Re <lucio.dere@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] upgrading the 9legacy shell (was: Gmail vs Upas)
Date: Tue, 3 Dec 2019 06:10:55 +0200 [thread overview]
Message-ID: <CAJQ9t7gHYdrJci8O_XaW6g04==z9he8iz5QxzWO7Usk6a8pQuQ@mail.gmail.com> (raw)
On 12/3/19, ori@eigenstate.org <ori@eigenstate.org> wrote:
>
> 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.
>
I'm quite obsessed with converging the very best of all 9worlds into a
single 9heritage version as an on-going project, but I am not very
good at staying focused. Updating rc I think is both a very good start
and a potential curse: the divergence in 9front is quite significant.
Plus, we need git9 and better for the community to contribute to a
neutral project (my opinion, of course).
What feels right to me is to focus on git9 before going any further
and make it as 9friendly as possible, to all 9fans. Would that
conflict with anyone's pet use of Plan 9?
If it makes sense, the git9 project could supply an upgraded rc as an
additional incentive.
But most of all, I think projects like these need participation and a
record of decisions taken. I know Go have a proposal system, could we
attempt to create something similar? Ori did point out in his
presentation that /sys/doc has great value in the Plan 9 ecosystem and
I could not agree more.
Lucio.
next reply other threads:[~2019-12-03 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 4:10 Lucio De Re [this message]
2019-12-03 6:17 ` ori
2019-12-03 10:19 ` Richard Miller
2019-12-03 11:42 ` Lucio De Re
2019-12-03 15:25 ` hiro
2019-12-03 20:01 ` Skip Tavakkolian
2019-12-03 20:31 ` hiro
2019-12-03 22:06 ` Skip Tavakkolian
2019-12-03 22:46 ` hiro
2019-12-03 22:53 ` andrey mirtchovski
2019-12-04 0:46 ` Skip Tavakkolian
2019-12-04 1:06 ` sstallion
2019-12-04 1:18 ` Alex Musolino
2019-12-04 4:55 ` Lucio De Re
2019-12-04 5:28 ` Alex Musolino
2019-12-04 14:59 ` hiro
2019-12-04 16:42 ` Nicolas S. Montanaro
2019-12-03 17:43 ` 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='CAJQ9t7gHYdrJci8O_XaW6g04==z9he8iz5QxzWO7Usk6a8pQuQ@mail.gmail.com' \
--to=lucio.dere@gmail.com \
--cc=9fans@9fans.net \
/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).