dwl10@uts.amdahl.com (Dave Lowrey) (05/25/89)
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!
--
"What is another word | Dave Lowrey | [The opinions expressed MAY be
for 'Thesaurus'?" | Amdahl Corp. | those of the author and are not
| Houston, Texas | necessarily those of his
Steven Wright | amdahl!dwl10 | employer] (`nuff said!)csc21909@uns-helios.uns.edu (csc219-9) (05/26/89)
> 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.
raz%kilowatt@Sun.COM (Steve -Raz- Berry) (05/29/89)
> Has anyone been able to sucessfully "RunBack Snipit"? When I > try, I either Guru, or Snipit is brain-dead. No, don't do this. Scott put his own 'runback' type stuff into snipit. Runback is not necessary, and in this case dangerous. > I would really like to eliminate snipit's anoying habit of grabbing hold > of the current console windo, and never letting go! I know, this tee'd me off too. So I rewote it to let the CLI go. I have been using the modified snipit for about 6 mos now. No problems. < 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. Yep, this is what the problem is. < 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 solution was to close the filehandle when it was done, and every write would check to see if the filehandle was null before writing to it (I null it out before closeing it). I did this a while ago... perhaps I'll take another look at what I did, I do remember that I wasn't real comfortable with it. I'll send the modified binary to Bob when I'm done. < 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 Me neither. I like snipit a WHOLE lot though. Steve -Raz- Berry Disclaimer: I didn't do nutin! UUCP: sun!kilowatt!raz ARPA: raz%kilowatt.EBay@sun.com "Fate, it protects little children, old women, and ships named Enterprise"