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 15:47:44 -0400 [thread overview]
Message-ID: <199206290547.18427.rc.balez@vetsci.su.oz.au> (raw)
In-Reply-To: <92Jun26.001135edt.2536@groucho.cs.psu.edu>
From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
I don't think -s should imply -i, as the patch does. If I want both
I can type both.
Is -s going to be standard, or will most people decline to apply the
patch?
Scott and all,
I don't have a lot of time now, and have more mail to write yet, so
please forgive me if I am a little terse.
The point of -s is not `how should it work', but rather `how -must-
it work'. No one wants to add -s to rc just because they think
it's a good idea. They want (in some cases, need) to add -s to rc
_in order to be compatible with the de-facto standard for command
line arguments to UNIX shells_. That's the point. This is how
the -s argument works in sh and csh, and therefore, if rc is to
have a -s argument at all, this is how it MUST work in rc.
Personally, I have no need for -s and don't care whether it is
in or out: but if it is to be in, I insist that it work just as
it does in other shells. Equally, rc cannot define new semantics
for -c or -e, etc. I hope that's clear.
OK,
John.
next prev parent reply other threads:[~1992-06-28 19:54 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 [this message]
1992-06-28 20:34 ` Scott Schwartz
1992-06-28 21:01 ` John Mackin
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=199206290547.18427.rc.balez@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).