Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!evax!cs4344af
From: cs4344af@evax.arl.utexas.edu (Fuzzy Fox)
Newsgroups: comp.sys.cbm
Subject: Re: printing in direct mode?
Keywords: help
Message-ID: <1991Mar15.012707.12846@evax.arl.utexas.edu>
Date: 15 Mar 91 01:27:07 GMT
References: <1991Mar13.161420.28673@cbnews.att.com> <1991Mar13.201004.3965@nntp-server.caltech.edu>
Distribution: na
Organization: Computer Science Engineering Univ. of Texas at Arlington
Lines: 24

In article <1991Mar13.201004.3965@nntp-server.caltech.edu> rknop@nntp-server.caltech.edu (Robert Andrew Knop) writes:
>
>OPEN4,4,4 <return>
>CMD4:<command> <return>
>PRINT#4:CLOSE4 <return>
>
>Actually, since you've given the CMD4, you could probably get away with
>"PRINT:CLOSE4".

Sorry, that's not right, that last part.  The closing of the print
channel is not cancelled by sending out a blank line (with PRINT), but
by the use of the PRINT# command itself.  Any sort of PRINT# would
cancel the effect of the CMD command.  As it is, usually there is
nothing more to be printed, so PRINT#4 by itself is used.

Now I think I'll go out on a limb and say, if you don't want there to be
a return mark after the final PRINT#4 command, just use PRINT#4,;
instead, which prints nothing at all, but does close the channel.

-- 
David DeSimone, aka "Fuzzy Fox" on some networks.          /!/!
INET:    an207@cleveland.freenet.edu                      /  ..
Q-Link:  Fuzzy Fox                                        /   --*
Quote:   "Foxes are people too!  And vice versa."         /  ---