Subj : BullsEye path limitations?
To   : Digital Man
From : Belly
Date : Tue May 17 2022 20:40:10

  Re: BullsEye path limitations?
  By: Digital Man to Belly on Tue May 17 2022 05:14 pm

 > I guess the next thing I would do is add a couple log() calls to exec/typeas
 > 
 > else { // added opening brace
 >         log(format("Calling console.printfile(%s, %s)", f.name, mode));
 >         console.printfile(f.name, mode);
 > } // added closing brace
 > 
 > And then see what is logged when you try to use typeasc.js to display that f

My brain is hurting.

I added your logging. I did an 'exec ?typeasc.js blah'. I looked in every log I
could find. Nothing.

I added another log() just before the for() loop that parses the switches, so I
could see if typeasc.js was being called at all. Ran it a few times. Ran
bullseye to look at some bulletins. Checked every log I could find. Still
nothing.

I think I'm going insane.

     o
    (O) 
   BeLLy

---
 þ Synchronet þ bbs.brazi.net þ www.brazi.net þ WARNING: May contain nuts
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.