From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rc shell UNIX port repository
Date: Sun, 6 Dec 2009 10:24:37 -0500 [thread overview]
Message-ID: <64d44ec5fe391e1af0833337d2bf9dd1@brasstown.quanstro.net> (raw)
In-Reply-To: <<8e04b5820912052352w304556cdufac28cc2dd3f9ffe@mail.gmail.com>>
> * who is maintaining the UNIX port of rc shell? (is it still
> Tig?) (if so what's the email address?)
> * is there a development repository for the source code?
> * are there any unit-tests available for the rc shell? (because I
> want to test my patches of not breaking something;)
i believe byron's rc comes with a "make tripping", but of course
that tests byron's varient of the language.
i've been using byron's rc since before 1990 on unix. it's handy
to have around if p9p rc gets broken. it is acceptable for my
occasional interactive use. i use linux seldom these days.
i'd be interested in your patches, though.
- erik
next parent reply other threads:[~2009-12-06 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<8e04b5820912052352w304556cdufac28cc2dd3f9ffe@mail.gmail.com>
2009-12-06 15:24 ` erik quanstrom [this message]
[not found] <<0d3820e90fedfa15c374652fe64f06b4@ladd.quanstro.net>
2009-12-14 14:14 ` erik quanstrom
[not found] <<8e04b5820912140211nd4edf3ei851c5a5128438d96@mail.gmail.com>
2009-12-14 14:08 ` erik quanstrom
2009-12-14 15:15 ` Ciprian Dorin, Craciun
2009-12-14 16:14 ` erik quanstrom
2009-12-14 16:33 ` Ciprian Dorin, Craciun
2009-12-14 16:44 ` erik quanstrom
2009-12-06 7:52 Ciprian Dorin, Craciun
2009-12-06 11:36 ` Charles Forsyth
2009-12-06 12:58 ` Ciprian Dorin, Craciun
2009-12-06 13:37 ` Frederik Caulier
2009-12-06 13:37 ` Charles Forsyth
2009-12-06 18:38 ` Axel Belinfante
2009-12-14 9:49 ` weakish
2009-12-14 10:11 ` Ciprian Dorin, Craciun
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=64d44ec5fe391e1af0833337d2bf9dd1@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).