From: byron@netapp.com (Byron Rakitzis)
To: cks@hawkwind.utcs.toronto.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: Interesting things from the Plan 9 rc manpage
Date: Tue, 27 Oct 1992 20:17:47 -0500 [thread overview]
Message-ID: <9210280117.AA25914@netapp.netapp.com> (raw)
-s: Print out exit status after any command where the
status is non-null (false).
This can be done with an appropriate fn prompt in my rc.
-I: Do not run interactively, regardless of whether or
not standard input is attached to a terminal.
This can be done with "rc /dev/tty". What do they use this option
for anyway?
It's too slow and too big.
I think that's just a Bell Labs pissing contest. Over there your macho-
ness as a programmer is measured in inverse proportion to the number
of lines of code you produce for a given task. My money says Duff's rc
is smaller and faster than any than ksh, bash, etc. :-)
(Though I would not be surprised if an implementation of rc that did
not lazily parse functions from the environment were perceived as being
slow on startup. This was a key optimization in my implementation.)
next reply other threads:[~1992-10-28 1:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-10-28 1:17 Byron Rakitzis [this message]
1992-10-28 1:57 ` noel
1992-10-28 1:59 ` noel
1992-10-28 5:59 ` James Matthew Farrow
-- strict thread matches above, loose matches on Subject: below --
1992-10-28 15:27 Paul Haahr
1992-10-28 5:10 Chris Siebenmann
1992-10-28 4:07 Paul Haahr
1992-10-28 4:20 ` Jeremy Fitzhardinge
1992-10-28 4:27 ` Chris Siebenmann
1992-10-28 3:14 Paul Haahr
1992-10-28 3:39 ` Chris Siebenmann
1992-10-28 4:00 ` Jeremy Fitzhardinge
1992-10-27 10:52 Chris Siebenmann
1992-10-27 16:08 ` Scott Schwartz
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=9210280117.AA25914@netapp.netapp.com \
--to=byron@netapp.com \
--cc=cks@hawkwind.utcs.toronto.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).