From: John (Deceased persons have no earning capacity) Mackin <john@civil.su. oz.au>
To: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: All I want for Christmas ...
Date: Wed, 2 Dec 1992 22:48:47 -0500 [thread overview]
Message-ID: <199212031448.1918.rc.badug@civil.su.oz.au> (raw)
In-Reply-To: <9212030341.AA09702@oldp.astro.wisc.edu>
If I do:
; exec foo
foo not found
then rc dies (as do all other shells, I believe).
Not _all_ other shells, just most of 'em. The Pike (V8+) version of
sh continues after a failed exec. I don't think this is too big an
issue, but I lean to the side of continuing, on the basis that if
the user typed the exec interactively and made a typo or was confused,
they probably didn't want their shell to go away.
2. -s flag
This has been talked about on the list before. Boyd did this 'cos he
felt he had to. I sent Boyd's code to Rich Salz.
Personally, as I have said before, I see nothing at all wrong with
adopting command line usage that brings rc more into line with the
defacto standard set by sh, and therefore I am behind -s, if not
heavily. On the other hand, I find it disappointing that -s
proponents cannot muster anything better than the tired old `I
seem to need this on Ultrix, for reasons I can't explain' argument.
Hell, people! I have many Ultrix boxes here. They are good boxes!
The _first_ thing you do on an Ultrix box is build X11R5. The _second_
thing you do is rm -rf DEATHwindows, and set up xdm and R5. Come on
up to Freely Distributable X Windows, Your International Passport
To Bitmapped Graphics Pleasure! You'll Be So Glad You Did!
(Well hell, X is terrible, but it's a gazillion times better than
DEATHwindows. Of course you might have special graphics hardware,
watch that one. Luckily, we don't.)
OK,
John.
next prev parent reply other threads:[~1992-12-03 3:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-03 3:41 Alan Watson
1992-12-03 3:48 ` John Mackin [this message]
1992-12-03 4:28 Byron Rakitzis
1992-12-03 4:42 ` Scott Schwartz
1992-12-03 5:00 Noel Hunt
1992-12-03 5:04 ` Chris Siebenmann
1992-12-03 5:23 Byron Rakitzis
1992-12-03 6:18 ` Scott Schwartz
1992-12-03 6:22 Alan Watson
1992-12-03 7:16 Byron Rakitzis
1992-12-03 7:23 Byron Rakitzis
1992-12-03 14:36 Alan Watson
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=199212031448.1918.rc.badug@civil.su.oz.au \
--to=john@civil.su.oz.au \
--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).