rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: rsalz@osf.org
To: rc@hawkwind.utcs.toronto.edu
Subject: rc and rsh
Date: Wed, 1 Jul 1992 15:13:11 -0400	[thread overview]
Message-ID: <9207011913.AA00693@earth.osf.org> (raw)

I don't think I understand the problems people are having with rsh and rc.
Does this function do the 'right thing' ?
fn rsh host1 host2... { flag= host=$0 {
    ~ $1 -n && { shift ; flag=-n }
    ~ $0 rsh && { host=$1 ; shift }
    eval 'rsh $flag $host rc -lc ''' ^ $* ^ ''''
} }


             reply	other threads:[~1992-07-01 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-07-01 19:13 rsalz [this message]
1992-07-01 20:59 ` Scott Schwartz
1992-07-01 20:49 Donn Cave
1992-07-01 20:58 rsalz

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=9207011913.AA00693@earth.osf.org \
    --to=rsalz@osf.org \
    --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).