From: "Ciprian Dorin, Craciun" <ciprian.craciun@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] rc shell UNIX port repository
Date: Sun, 6 Dec 2009 09:52:04 +0200 [thread overview]
Message-ID: <8e04b5820912052352w304556cdufac28cc2dd3f9ffe@mail.gmail.com> (raw)
Hello all!
I'm a new (1 week) user of the rc shell (I want to migrate from
the Sh/Bash and their offsprings to rc after a lot of pain and misery
with them). :) And so far I like the rc look-and-feel (by look I mean
syntax and by feel I mean semantics.) as their quite minimal and with
just the right functionality. :)
So back to the point: I'm using rc-1.7.1 UNIX port of the rc
shell, downloaded from:
http://www.libra-aries-books.co.uk/software/download/rc/rc-1.7.1.tar.gz
and during my initial trials, I've found quite a few bugs related
with the `-e` (exit shell on non-0 exit code), which I've tried (and
think I've managed) to solve.
Now I'm trying to contribute back to the community, and I've sent
an email to Tig Goodwin (at tjg@star.le.ac.uk), which the mail server
rejected (it seems that the email is not valid any more). Then I've
sent an email to Byron Rakitzis (at byron@netapp.com), which worked
but no reply yet (maybe I'm on the to-do list. :) )
So my questions are:
* 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?
* is there a mailing list dedicated to the rc shell? (either
native or UNIX ported one?)
* are there any unit-tests available for the rc shell? (because I
want to test my patches of not breaking something;)
Thanks,
Ciprian.
P.S.: In my migration from Sh/Bash I've ended up deciding between
two candidates: scsh (Scheme Shell) (which is quite powerfull, being a
full R5RS Scheme implementation, with process management support, but
I've found a few rough edges (mainly related with error handling), and
it's quite heavy weight implementation with a large (in file number)
footprint), and rc (quite lightweight (only one executable statically
linked)).
So are there any other worthy alternatives?
next reply other threads:[~2009-12-06 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 7:52 Ciprian Dorin, Craciun [this message]
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
[not found] <<8e04b5820912052352w304556cdufac28cc2dd3f9ffe@mail.gmail.com>
2009-12-06 15:24 ` 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
[not found] <<0d3820e90fedfa15c374652fe64f06b4@ladd.quanstro.net>
2009-12-14 14:14 ` erik quanstrom
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=8e04b5820912052352w304556cdufac28cc2dd3f9ffe@mail.gmail.com \
--to=ciprian.craciun@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).