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: Re: All I want for Christmas ...
Date: Thu, 3 Dec 1992 01:22:41 -0500	[thread overview]
Message-ID: <9212030622.AA10599@oldp.astro.wisc.edu> (raw)

1. exec

The only time I use exec interactively is when I install a new version
of rc.  I think it would be a poor choice to differentiate the
behaviour of exec based on the interactiveness of the shell.

Part of the reason that I would like the change is that I often use
exec in scripts ... but I also often make mistakes in scripts.
Dumping the environment to stderr after a failed exec would be a
useful debugging aid.  It also just seems "the right thing to do."
However, Byron's reservations are valid.

2. -s

Hey, yeah, now you mention it I remember that coming round.  My
apologies for bringing it up again.

3. Let me make one more comment, which arises from a recent discussion
in comp.unix.shell:

	; rc <<EOF
	...
	. /dev/tty
	EOF

is interactive after the here document, but

	; rc <<EOF
	...
	exec </dev/tty
	EOF

is not.  Should this be so?  (And, I guess, is this even important?)

Please don't take my suggestions as criticism: I have silently thanked
Tom Duff and Byron more time than I can recall for providing me with a
shell which behaves in a simple, rational, and predictable manner in
almost every situation I have come across.  What's more, it even does
what the man page says it does ...

Alan.


             reply	other threads:[~1992-12-03  6:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-12-03  6:22 Alan Watson [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  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  4:28 Byron Rakitzis
1992-12-03  4:42 ` Scott Schwartz
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=9212030622.AA10599@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).