rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Carlo Strozzi <carlos@linux.it>
To: rc <rc@hawkwind.utcs.toronto.edu>
Subject: Re: building rc on QNX4
Date: Thu, 27 Apr 2000 13:39:48 -0400	[thread overview]
Message-ID: <20000427193948.A15307@tango.texne.com> (raw)
In-Reply-To: <20000426110230.A12715@localhost>; from sroberts@uniserve.com on Wed, Apr 26, 2000 at 11:02:31AM -0400

On Wed, Apr 26, 2000 at 11:02:31AM -0400, Sam Roberts wrote:
 >
 >rc looks really good to me, so I built it over the weekend, and

I agree, it is a neat shell, much better than Bourne and derivatives
for scripting. I am awful at C programming, but I think adding a few
addons to rc should be easy. The only thing that I really miss is a
'read' builtin. Using line(1) did not work, at least on Linux, apart
from the fact that being line(1) an external process it is not really
efficient, as it is often called from inside a loop.

Also, I think that the name 'rc' is sometimes a too short one. On AIX,
for instance, it conflicts with the system startup script /etc/rc.
I use Linux, so that's not a problem for me, nevertheless I would
really like that the default 'make install' stuff set up a symlink
to rc with a longer and more meaningful name, like 'rcsh'.

cheers  -carlo
-- 
Attachments only in HTML/RTF/Postscript please !                    
Per favore solo attachments in formato HTML/RTF/Postscript !


  parent reply	other threads:[~2000-04-28 20:33 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <sroberts@uniserve.com>
2000-04-26 15:02 ` Sam Roberts
2000-04-27 16:56   ` Scott Schwartz
2000-04-27 20:41     ` Sam Roberts
2000-04-28  7:28       ` vrl (was: Re: building rc on QNX4) Gert-Jan Vons
2000-04-28 18:38         ` Sam Roberts
2000-05-02  8:16           ` Gert-Jan Vons
2000-04-28 19:03         ` rc not session leader? Sam Roberts
2000-04-27 17:39   ` Carlo Strozzi [this message]
2000-05-02 14:41     ` building rc on QNX4 Tim Goodwin
2000-05-04 15:18       ` Carlo Strozzi
2000-05-08  8:29         ` Tim Goodwin
2000-05-08  8:58           ` Chris Siebenmann
2000-05-08  9:15             ` Tim Goodwin
2000-05-08 23:25               ` Stephen Tell
2000-05-10  0:37                 ` builtins Scott Schwartz
2000-05-12  7:22                   ` builtins Carlo Strozzi
2000-05-08 11:50           ` building rc on QNX4 David Luyer
2000-05-08 13:28           ` Carlo Strozzi
2000-05-04  8:45 Byron Rakitzis
2000-05-06 10:28 ` Carlo Strozzi
2000-05-07 17:46   ` Paul Haahr
2000-05-08  8:01     ` Carlo Strozzi
2000-05-06 16:35 ` Jeremy Fitzhardinge
2000-05-04 13:46 Sam Roberts
2000-05-06 21:47 Byron Rakitzis
2000-05-08 10:19 Bengt Kleberg
2000-05-08 15:15 Smarasderagd
2000-05-09  8:22 ` Carlo Strozzi
2000-05-08 15:23 Sam Roberts
2000-05-09  8:25 ` Carlo Strozzi
2000-05-09  4:34 Smarasderagd
2000-05-11 12:26 ` Gert-Jan Vons

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=20000427193948.A15307@tango.texne.com \
    --to=carlos@linux.it \
    --cc=carlos@texne.com \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /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).