Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!unsvax!uns-helios!csc21909
From: csc21909@uns-helios.uns.edu (csc219-9)
Newsgroups: comp.sys.amiga
Subject: Re: Snipit & Runback
Message-ID: <644@unsvax.NEVADA.EDU>
Date: 25 May 89 17:16:56 GMT
References: <90hv02UP2cLB01@amdahl.uts.amdahl.com>
Sender: news@unsvax.NEVADA.EDU
Reply-To: csc21909@uns-helios.uucp (csc219-9)
Organization: Univ of Nevada System Computing Services - Las Vegas
Lines: 19

> Has anyone been able to sucessfully "RunBack Snipit"? When I
> try, I either Guru, or Snipit is brain-dead.
> 
> I would really like to eliminate snipit's anoying habit of grabbing hold
> of the current console windo, and never letting go!

     I've studied the source code to snipit, trying to fix this same thing.
the problem seems to be two-fold.  First of all, it does all output to "*"
but I think you should be able to use the default output of the subsequent
snipit commands.
     Second, it can't handle a null value for this filehandle.  I don't have
Manx 3.6, which is what it takes to compile snipit 1.2, so I can't fix it.
     My question is, would there be any souls out there kind enough to 
fix this?  I'd like to put snipit in my startup sequence, but I can't stand
having uncloseable windows on my screen, because sooner or later I'll try
to close it.

				Eric Schwertfeger
				No address, account pumkinizes tomorrow.