From: sl@9front.org
To: 9fans@9fans.net
Subject: Re: [9fans] 9front sam in plan9port.
Date: Sat, 21 May 2016 14:25:45 -0400 [thread overview]
Message-ID: <39c733b434fd11855534f6a47714a162@lrsb.attlocal.net> (raw)
In-Reply-To: <CAPd04b7aF12sSV5WmfO5ERM6H3vPBV5zLKWfwN_fFzR0U1uX8A@mail.gmail.com>
> Ok, the wording on that site is a bit odd to me. The name plan9port is a
> project Russ Cox wrote, so the wording
>
> A port of 9front's version of sam(1) to unix (plan9port)
>
> seemed to imply porting 9front's sam(1) to plan9port. That didn't make
> sense to me since Russ's plan9port sam goes back many many years earlier
> than the 2014 timestamp in that repo you pointed at.
Yes, and 9front's sam has some additional features (like chording) that are
not found in p9p's sam.
If I understand correctly, the author wanted to use those features, which is
why he set out to replace the same that was already in p9p with this newer
modification.
sl
next prev parent reply other threads:[~2016-05-21 18:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 15:35 trebol55555
2016-05-21 15:50 ` James A. Robinson
2016-05-21 16:31 ` trebol55555
2016-05-21 17:07 ` James A. Robinson
2016-05-21 18:25 ` sl [this message]
2016-05-21 18:25 ` Mark van Atten
2016-05-21 18:30 ` sl
2016-05-21 18:33 ` erik quanstrom
2016-05-21 18:41 ` sl
2016-05-21 18:41 ` Mark van Atten
2016-05-21 19:49 trebol55555
[not found] ` <CABJnqBTrK38zqn6E+MJE_JbNG2nKv2jqXizZ4g6h=MrpUuxFUg@mail.gmail.com>
[not found] ` <CABJnqBSDQoyFH=2=63-=yY2igyab0uZJ9VayRXr=+A=O1SHubA@mail.gmail.com>
2016-05-22 5:29 ` Iruatã Souza
2016-05-22 11:07 ` Mart Zirnask
2016-05-22 12:23 ` trebol55555
2016-05-22 17:45 ` Mark Lee Smith
2016-05-23 7:25 ` Mart Zirnask
2016-05-23 20:27 ` Mart Zirnask
2016-05-23 21:28 ` Skip Tavakkolian
2016-05-23 21:38 ` Ryan Gonzalez
2016-05-24 2:27 ` Dave MacFarlane
2016-05-24 5:02 ` Matthew Veety
2016-05-22 18:08 ` Mark Lee Smith
2016-05-22 20:15 ` trebol55555
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=39c733b434fd11855534f6a47714a162@lrsb.attlocal.net \
--to=sl@9front.org \
--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).