From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Sat, 21 May 2016 14:25:45 -0400
From: sl@9front.org
To: 9fans@9fans.net
Message-ID: <39c733b434fd11855534f6a47714a162@lrsb.attlocal.net>
In-Reply-To: <CAPd04b7aF12sSV5WmfO5ERM6H3vPBV5zLKWfwN_fFzR0U1uX8A@mail.gmail.com>
References: <CAPd04b7vZ8gko2fd=oui3JR6XsgeoyOWDmA-72A0tyERR8aeaQ@mail.gmail.com>
	<72921bad1cfbc2b3e2a46a5fed0dedc0@debpi>
	<CAPd04b7aF12sSV5WmfO5ERM6H3vPBV5zLKWfwN_fFzR0U1uX8A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] 9front sam in plan9port.
Topicbox-Message-UUID: 924fb4f0-ead9-11e9-9d60-3106f5b1d025

> 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