From: Robert.van.Liere@cwi.nl
To: rc@archone.tamu.edu
Subject: call unix
Date: Wed, 1 Jan 1992 07:34:09 -0600 [thread overview]
Message-ID: <9201011334.AA24838@paling.cwi.nl> (raw)
I'm probably missing something that is quite obvious but
does anyone out there use call unix ('cu') to transfer
files to/from home ?
Call unix reads data from standerd input and, except for lines
starting with ~ (thats right, the tilde !), passes it to the remote
system. Lines starting with a tilde has special meanings. Unfortunately,
rc doesn't like this at all and (rightly so) complains about syntax
errors, etc, etc ..
Is there something I can do so that I can run cu with rc ? (what I do
now is first go into /bin/sh before invoking cu).
-- Robert
PS : I *have* to use cu because slip is just to slow (no ISDN (yet)
here in Amsterdam).
Robert van Liere, Department of Interactive Systems,
Center for Mathematics and Computer Science (CWI)
Kruislaan 413, 1098 SJ Amsterdam, The Netherlands
email: robertl@cwi.nl | tel: +31-20-592-4053 | fax: +31-20-592-4199
reply other threads:[~1992-01-01 13:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9201011334.AA24838@paling.cwi.nl \
--to=robert.van.liere@cwi.nl \
--cc=rc@archone.tamu.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).