rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: -c arguents
Date: Mon, 1 Nov 1993 13:35:41 -0500	[thread overview]
Message-ID: <9311011835.AA25777@oldp.astro.wisc.edu> (raw)

I've just discovered a minor incompatibility between rc and sh:

	sh -ce foo	# execute foo and exit on any error
	rc -ce foo	# execute e with an argument of foo

rc is behaving according to the manual page, so this is not a bug,
however, I wonder if the behaviour should be changed to follow that of
sh?

I came across this using make on our new SGI machine -- it executes
commands with $SHELL -ce ... and I had forgotten to explicity set SHELL
to sh within the Makefile.

Alan.


             reply	other threads:[~1993-11-01 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-11-01 18:35 Alan Watson [this message]
1993-11-01 18:47 ` John Mackin
1993-11-01 18:50 ` Robert van Liere
1993-11-01 19:16 Tom Culliton x2278

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=9311011835.AA25777@oldp.astro.wisc.edu \
    --to=alan@oldp.astro.wisc.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).