Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu
From: duncan@csd4.csd.uwm.edu (Shan D Duncan)
Newsgroups: comp.sys.amiga
Subject: Re: Our hero....tad! :-)
Message-ID: <6326@uwm.edu>
Date: 15 Sep 90 18:01:14 GMT
References: <TADGUY.90Sep14155249@abcfd21.larc.nasa.gov>
Sender: news@uwm.edu
Reply-To: duncan@csd4.csd.uwm.edu
Lines: 32

From article <TADGUY.90Sep14155249@abcfd21.larc.nasa.gov>, by tadguy@abcfd01.larc.nasa.gov (Tad Guy):
> In article <30491@nigel.ee.udel.edu> new@ee.udel.edu (Darren New) writes:
>> In article <1990Sep14.202505.2828@csc.anu.oz.au> myb100@csc.anu.oz.au writes:
>> >On another note, would it be possible to add another command which allows
>> >you to examine a .readme file over the link ? 
>> 
>> Why not use
>> ftp> get README /dev/tty
> 
> Don't assume everyone uses UNIX (yet).
> 
> 	...tad


I always used:


ftp> get README -


From our ftp manual (yes it is bsd unix).  But should this be
standard for all ftp implementations?

from man ftp:
...

FILE NAMING CONVENTIONS
     Files specified as arguments to ftp commands are processed
     according to the following rules.

     1)   If the file name "-" is specified, the stdin (for read-
	  ing) or stdout (for writing) is used.