Subj : directory() results affected by console.yesno()..?
To : Nightfox
From : Digital Man
Date : Sat Mar 30 2024 10:10 am
Re: directory() results affected by console.yesno()..?
By: Nightfox to deon on Fri Mar 29 2024 10:33 pm
> Re: directory() results affected by console.yesno()..?
> By: deon to Nightfox on Fri Mar 29 2024 09:40 pm
>
> > DM>> The directory() method is implemented as js_directory() in
> > DM>> js_global.c, so if you wanted to make experimental changes (e.g.
> > add
> > DM>> debug output or whatever), that's where you'd do that.
>
> >> Thanks. I may try that.
>
> de> Use some log(LOG_DEBUG,...) before that call and see if it makes a
> de> difference.
>
> I found out what the problem was. I was using js.exec_dir in my call to
> directory(), and it looks like js.exec_dir can be indirectly changed (such
> as by console.yesno() running yesnobar.js from sbbs/exec). js.exec_dir has
> the directory of the currently running script (and I thought it would be the
> same throughout the same script, but it seems that's not the case).
Yeah, it's a bug that I'll fix.
--
digital man (rob)
This Is Spinal Tap quote #14:
The Boston gig has been cancelled. [Don't] worry, it's not a big college town.
Norco, CA WX: 47.4�F, 94.0% humidity, 2 mph WNW wind, 0.56 inches rain/24hrs
---
� Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net