From: John (_You_ hide, they seek.) Mackin <john@vetsci.su.oz.au>
To: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: recent -s patch
Date: Sun, 28 Jun 1992 17:01:19 -0400 [thread overview]
Message-ID: <199206290701.19089.rc.balij@vetsci.su.oz.au> (raw)
In-Reply-To: <92Jun28.163516edt.2538@groucho.cs.psu.edu>
Scott is quite right. Just goes to show how little I've ever understood
that damned -s option anyway. Someone who cares about it should fix the
patch so that -s doesn't imply -i. Hey, can anyone on the list tell us
all if they have any reason at all for wanting -s? Inquiring minds
want to know. So far, we have Rich's reason, which is that -s is
passed to the invoked shell by `the OSF/1 script command'. Any
other takers?
To put it another way, can anyone show me any real use for -s? That
is, why is the damned idea good? Try as I might I can't see any.
(This shouldn't be construed as an argument for keeping it out of
rc. To the contrary, I will always be willing to entertain rc features
that keep it compatible (in appropriate ways) with traditional shells.)
OK,
John.
next prev parent reply other threads:[~1992-06-28 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-06-26 4:11 Scott Schwartz
1992-06-28 19:47 ` John Mackin
1992-06-28 20:34 ` Scott Schwartz
1992-06-28 21:01 ` John Mackin [this message]
1992-06-29 1:36 Bob Gibson
1992-06-29 23:19 ` David J. Fiander
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=199206290701.19089.rc.balij@vetsci.su.oz.au \
--to=john@vetsci.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).