From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] new rc parser: do we want it?
Date: Thu, 15 Oct 2020 19:32:03 -0400 [thread overview]
Message-ID: <CE6A13ED-6482-46F1-933E-756CA66F05C3@stanleylieber.com> (raw)
In-Reply-To: <CA+ULb+tKLJWyxcZi6CZVGQMEEatFOXMMLLWdRA7nVk2fz20MxQ@mail.gmail.com>
On October 15, 2020 7:14:50 PM EDT, Roman Shaposhnik <roman@shaposhnik.org> wrote:
>On Thu, Oct 15, 2020 at 10:23 AM Anthony Martin <ality@pbrane.org>
>wrote:
>>
>> Stanley Lieber <sl@stanleylieber.com> once said:
>> > rc's v10 online man page refers to it as "the plan 9 shell." my
>print
>> > edition is in storage, but i don't think it mentioned plan 9. the
>> > online version may represent a later extraction from the labs'
>running
>> > system. plan 9 was percolating at least as early as 1988. it's
>unclear
>> > exactly when rc was first written, but based on the timeline of
>> > releases it first shipped in v10.
>>
>> The v10 tree on TUHS has /vol2/rc/rc.ms¹ but it's dated 1993-06-19.
>> The title from that version is "Rc — A shell for Plan 9 and UNIX".
>>
>> I don't have a copy of the printed v10 manual to check what it
>> was in 1989/1990. I'd be curious to see what yours says.
>
>My printed Second Edition manual says:
>
>NAME
> rc, cd, eval, exec... - command language
>SYNOPSIS
> rc ...
>DESCRIPTION
> Rc is the Plan 9 shell.
>
>Thanks,
>Roman.
>
>Thanks,
>Roman.
everyone:
i screwed up and cc'd rob on my post (thought better of it and forwarded him the message, but forgot to remove the cc -- this mailing list silently drops messages from addresses that are not suscribed). please don't cc him on every single reply.
thanks,
sl
next prev parent reply other threads:[~2020-10-15 23:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5EF01FE4B564E504DD635D7E391EE0C8@ewsd.inri.net>
2020-10-12 20:44 ` Romano
2020-10-15 10:11 ` Ethan Gardener
2020-10-15 12:11 ` Stanley Lieber
2020-10-15 16:41 ` Romano
2020-10-15 17:22 ` Anthony Martin
2020-10-15 23:14 ` Roman Shaposhnik
2020-10-15 23:32 ` Stanley Lieber [this message]
[not found] <1975289B8C108B2FCF360524D16AA25B@ewsd.inri.net>
2020-10-07 10:00 ` Ethan Gardener
[not found] <01DB736907F1AF8292BF2D9C25564677@ewsd.inri.net>
2020-10-07 4:46 ` ori
2020-10-07 13:06 ` kvik
2020-10-07 3:15 ori
2020-10-07 3:54 ` [9front] " sl
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=CE6A13ED-6482-46F1-933E-756CA66F05C3@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).