Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!rutgers!lll-crg!hoptoad!farren From: farren@hoptoad.uucp (Mike Farren) Newsgroups: net.micro.amiga Subject: Re: vt100 2.2 finally works for me Message-ID: <1275@hoptoad.uucp> Date: Mon, 10-Nov-86 01:33:32 EST Article-I.D.: hoptoad.1275 Posted: Mon Nov 10 01:33:32 1986 Date-Received: Tue, 11-Nov-86 00:37:49 EST References: <219@ci-dandelion.UUCP> Reply-To: farren@hoptoad.UUCP (Mike Farren) Organization: Nebula Consultants in San Francisco Lines: 27 In article <219@ci-dandelion.UUCP> dgg@ci-dandelion.UUCP (Dave Grubbs) writes: > > - Kermit Get works fine, but what is "Kermit Receive" supposed to do? > I thought it would be something like 1) prompt for file (or wildcard) > 2) send the string "kermit -s" (or "kermit -i -s" if Comm/Xfer/image > is set), then 3) go into response mode. What is it for? The only > use I can think of is as a "server", which is not what a terminal > emulator is for. > > - (Warning: trivial semantic complaint ;-)) I believe the "get" and > "receive" labels are switched. Receive is a "continuous" condition, > (send/receive) whereas "get" has the connotation of "go grab one". > The labels aren't switched. "Get" implies that the other end of the line has a Kermit server active. It will send the filename you request to the server, which will then send you the file. "Receive", on the other hand, implies that you have entered a command such as "kermit -s " on the remote system, and then entered receive mode on your end, to receive the requested files. -- ---------------- "... if the church put in half the time on covetousness Mike Farren that it does on lust, this would be a better world ..." hoptoad!farren Garrison Keillor, "Lake Wobegon Days"