From: Alan Watson <alan@oldp.astro.wisc.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: All I want for Christmas ...
Date: Wed, 2 Dec 1992 22:41:13 -0500 [thread overview]
Message-ID: <9212030341.AA09702@oldp.astro.wisc.edu> (raw)
Well, rc v1.5 was mentioned, so I figure it's time to get out my wish
list and see what Santa brings for Christmas.
1. Error handling after exec
If I do:
; exec foo
foo not found
then rc dies (as do all other shells, I believe). Would it be
difficult to continue after such an error, so that the user could
decide on the appropriate action to take? This would more closely
parallel the behaviour of the system call, but is it the behaviour we
want from a shell?
2. -s flag
Other shells have a -s flag, meaning "read commands from stdin unless
told otherwise." It seems pretty useless to me, but my X server
executes my .X11Startup by the equivalent of "$SHELL -s <.X11Startup".
I'm not sure if this is standard (what's wrong with execlp?), but it
would not surprise me if this feature was specific to Ultrix servers.
Ultrix rather frowns of the MIT way of configuring X. (Oh, the drama
and joy of Ultrix.) I get around this by using a five line C program
as my "shell"; it eliminates any "-s" at argv[1] and then execs rc.
Is there any support for adding an (essentially dummy) -s flag to rc
for the sake of compatibility with other shells?
next reply other threads:[~1992-12-03 3:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-12-03 3:41 Alan Watson [this message]
1992-12-03 3:48 ` John Mackin
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=9212030341.AA09702@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).