From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: byron@netapp.com (Byron Rakitzis)
Cc: alan@oldp.astro.wisc.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: All I want for Christmas ...
Date: Wed, 2 Dec 1992 23:42:50 -0500 [thread overview]
Message-ID: <92Dec2.234259est.2581@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 02 Dec 92 23:28:57 EST." <9212030428.AA03379@netapp.netapp.com>
| re: exec. I would rather not change the behavior of exec. For example,
| what if some script uses exec for flow control; an exec which continued
| on failure would change the behavior of the script.
I'd rather have the shell do the right thing and fix the scripts.
next prev parent reply other threads:[~1992-12-03 4:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-03 4:28 Byron Rakitzis
1992-12-03 4:42 ` Scott Schwartz [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-12-03 14:36 Alan Watson
1992-12-03 7:23 Byron Rakitzis
1992-12-03 7:16 Byron Rakitzis
1992-12-03 6:22 Alan Watson
1992-12-03 5:23 Byron Rakitzis
1992-12-03 6:18 ` Scott Schwartz
1992-12-03 5:00 Noel Hunt
1992-12-03 5:04 ` Chris Siebenmann
1992-12-03 3:41 Alan Watson
1992-12-03 3:48 ` John Mackin
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=92Dec2.234259est.2581@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=alan@oldp.astro.wisc.edu \
--cc=byron@netapp.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).