https://gitlab.synchro.net/sbbs/sbbs/-/commit/256251869f924e3acc9ffb8d
Modified Files:
src/sbbs3/exec.cpp
Log Message:
Previous commit fixed issue with JS_GC before JS_ENDREQUESTSo revert the order back to the way it was in aa2bcd61e9017816d06e581eef478(don't you love these git references?).Also, the previous fix for js_execfile() calls for global hot-key events alsofixed the EX_JS_CX feature I was working on (js_execmodule)!
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/sbbs/sbbs/-/commit/175d0fbc996e5292480bab8e
Modified Files:
src/sbbs3/exec.cpp
Log Message:
Always evaluate js.on_exit() installed expressions.I noticed that when executing an external JS with the new "Use Shell / New Context" option set to "Yes", that any expressions (strings) installed via js.on_exit() were not being executed upon exit from the script. These on-exit strings are important for restoring global state information (e.g. control key pass-through, console mode) to the original state before the JS mod made any changes.I'm not sure why the special treatment of "scope == NULL" is through-out this function. Going back to v3.16, it appears this was special treatment for JS mods invoked via global hot key event (when scope != NULL). When invoking an xtrn JS mod with the new Context option, the scope argument is not NULL, so this check was defeating the parsing of the "exit_code" and the evaluation of any js.on_exit() installed expressions for no apparent reason. I can't think why global hot key events should be excluded from this logic either.
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/b287a8d0887dce091a965ede
Modified Files:
src/sbbs3/exec.cpp
Log Message:
Log a better error when attempting to execute a non-existent module.Don't complain that exec/<modname>.bin can't be opened. Instead, complain that <modname> doesn't exist and therefore can't be executed. The old message could be misleading/confusing if the expected module is a JS mod (not Baja-compiled .bin mod).
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/10d7a690029318dc4ff59ffa
Modified Files:
src/sbbs3/exec.cpp
Log Message:
Merge branch 'master' of gitlab.synchro.net:main/sbbs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/47f8c020a88939d18a033542
Modified Files:
src/sbbs3/exec.cpp
Log Message:
JS module command-lines now supported quoted arguments (w/white-space)Example:Command-line: ?showargs " a b c "d "e f"argc = 3argv[0] = ' a b c 'argv[1] = 'd'argv[2] = 'e f' This resolves a long-standing TODO comment.Also, fixed a problem where multiple spaces between the module name and the first argument would result in argv[0] being set to an empty string.
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/30ebfa0a61f9fbffdd42cc93
Modified Files:
src/sbbs3/exec.cpp
Log Message:
Have js_execfile() save/restore callbacksThis should allow callbacks to not interfere between (say) shellsand doors.
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)