From: Tim Goodwin <tjg@star.le.ac.uk>
To: rc@hawkwind.utcs.utoronto.ca
Subject: Anybody use `rc -s'?
Date: Wed, 20 Jan 1999 05:13:29 -0500 [thread overview]
Message-ID: <AAAYXDalrEkACeS/@ltsun0.star.le.ac.uk> (raw)
A discussion has arisen between myself and a trusty beta tester over
the `-s' flag. This flag was new (and undocumented) in rc-1.5betadev1;
it causes rc to put any arguments into $* (instead of treating them as
files to be read); rc then reads from standard input.
At present, `-s' implies `-i', and we suspect that this is wrong. I
would be interested to hear from anybody who is actually using `rc -s'
(or `sh -s', for that matter), since we're having trouble coming up with
any realistic examples.
Any comments appreciated.
Tim.
P.S. I've received a small amount of feedback on rc-1.5b4, which
has all been positive. More feedback (especially if you've run into
problems with it) is always welcome!
next reply other threads:[~1999-01-20 23:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-20 10:13 Tim Goodwin [this message]
1999-01-21 0:53 ` Scott Schwartz
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=AAAYXDalrEkACeS/@ltsun0.star.le.ac.uk \
--to=tjg@star.le.ac.uk \
--cc=rc@hawkwind.utcs.utoronto.ca \
/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).