Subj : BullsEye path limitations?
To   : Belly
From : Digital Man
Date : Wed May 18 2022 11:27:46

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

 >   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.

It would go to the terminal server log output. In Synchronet Control Panel for windows, that's the "Terminal Server" tab.

 > 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.

Maybe you have another coyp of typeasc.js somewhere on your system (e.g. mods directory) and that's being executed instead of exec/typeasc.js.
-- 
                                            digital man (rob)

Synchronet/BBS Terminology Definition #9:
BPS = Bits Per Second
Norco, CA WX: 66.2øF, 75.0% humidity, 3 mph SE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.15-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.