rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: John (_You_ hide, they seek.) Mackin <john@vetsci.su.oz.au>
To: The rc Mailing List <rc@hawkwind.utcs.toronto.edu>
Subject: Re: Adding the '-s' flag?
Date: Wed, 17 Jun 1992 09:01:51 -0400	[thread overview]
Message-ID: <199206172301.17232.rc.balek@vetsci.su.oz.au> (raw)
In-Reply-To: <9206171300.AA13571@earth.osf.org>

I have been carrying on a discussion with Rich about the -s flag, and he
made the following comment:

     I would like a version of script that took a commandline to run; wold
    be useful at times.

More and more and more I am so excruciatingly glad that I changed over to
rc when I did.  Sure, the quoting is clean, sure, we have confidence in
interactive constructs because we understand the grammar, but never mind
all that!  The biggest reason to use rc is, it just pays off again and
again in total functionality!!  If you have a shell which is sophisticated,
powerful, understandable _and_ lacking in `dark corners,' well, you really
can accomplish anything.

You want script to be able to run a command?  Absolutely too easy!  Don't
change the real script, just install this (which I just wrote but have
tested) in $path in front of it, called script.  Giving it a usage
compatible with real script (-a for append, supply script filename)
is left as an exercise for the reader.

[By the way Rich: unless your version of script has powers and abilities
far beyond those of mortal versions, why not trash it and render the -s
question moot?]

OK,
John.

#!/full/path/to/rc

SHELL = /full/path/to/rc	# if you think anyone will run it with $SHELL
				# set otherwise
if ( ! ~ $#* 0 ) eval fn prompt '{' $* ';' exit '}'
exec /full/path/to/real/script


       reply	other threads:[~1992-06-17 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9206171300.AA13571@earth.osf.org>
1992-06-17 13:01 ` John Mackin [this message]
1992-06-15 18:53 rsalz
1992-06-15 19:50 ` 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=199206172301.17232.rc.balek@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).