From: Stephen Tell <tell@cs.unc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: building rc on QNX4
Date: Mon, 8 May 2000 19:25:25 -0400 [thread overview]
Message-ID: <Pine.GHP.4.10.10005081920100.29426-100000@rukbat.cs.unc.edu> (raw)
In-Reply-To: <TxUAAKuFFjmmrwMA@ltsun0.star.le.ac.uk>
On Mon, 8 May 2000, Tim Goodwin wrote:
> Date: Mon, 8 May 2000 05:15:01 -0400
> From: Tim Goodwin <tjg@star.le.ac.uk>
> To: rc@hawkwind.utcs.toronto.edu
> Subject: Re: building rc on QNX4
>
> > In order to make this work, you need to find a utility that is
> > guaranteed to read no more than the first line of standard input.
>
> Yup. What if such a utility were distributed with rc, or as part of an
> rc-utils package?
I suppose that would be sufficient. The workaround I've used
has been this:
var = `{sh -c 'read t; echo $t'} # read var
Starting up sh just to avoid the little bit of code that a read
builtin would add to rc itself or an included utility seems a bit
rediculous.
--
Steve Tell | tell@cs.unc.edu | http://www.cs.unc.edu/~tell | KF4ZPF
On Leave from UNC working at Chip2Chip, Inc. tell@chip2chip.com/919-929-0991
next prev parent reply other threads:[~2000-05-09 22:53 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
2000-05-08 8:58 ` Chris Siebenmann
2000-05-08 9:15 ` Tim Goodwin
2000-05-08 23:25 ` Stephen Tell [this message]
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=Pine.GHP.4.10.10005081920100.29426-100000@rukbat.cs.unc.edu \
--to=tell@cs.unc.edu \
--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).