From: Tim Goodwin <tjg@star.le.ac.uk>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: building rc on QNX4
Date: Mon, 8 May 2000 04:29:54 -0400 [thread overview]
Message-ID: <BxMAABh7Fjm+LgcA@ltsun0.star.le.ac.uk> (raw)
In-Reply-To: <20000504171816.B12075@polka.mi.linux.it>
> A more important issue IMHO is whether Rc should provide a built-in
> read function, similar to the one offered by most Bourne shells;
There is no *need* to make `read' a builtin: see the EXAMPLES file in
the distribution for an alternative. One of rc's design goals is to
avoid unnecessary builtins. So, no, I don't think this is likely to
happen.
(I accept that there is some work to be done, first in terms of
documentation: the EXAMPLES file is not as visible as it should be.
Also, I have some vague ideas for the future about a package of small
utilities to work with rc (and other shells); one of these would be
something like `line'---unfortunately not available everywhere---and
make a building block for an efficient `read' function.)
> another
> one is whether it will ever make it possible not to export everything to
> the environment by default.
I brought this up a few months ago, and the consensus seemed to be that
the current scheme works well enough in practice. Have you encountered
a problem?
Tim.
next prev parent reply other threads:[~2000-05-08 9:03 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 ` building rc on QNX4 Carlo Strozzi
2000-05-02 14:41 ` Tim Goodwin
2000-05-04 15:18 ` Carlo Strozzi
2000-05-08 8:29 ` Tim Goodwin [this message]
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=BxMAABh7Fjm+LgcA@ltsun0.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--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).