draw the top line and first left vertical row in a file list box.  The rest
of the box was drawn in whatever attribute text.dat left it in.

Optionally, external modules may be executed in place of "built-in" operations
for:
- reading mail (email or netmail)
- scanning posts (searching/scanning/reading a single sub-board)
- scanning sub-boards (all, one, or a group)

Each of these may be configured (in SCFG->System->Loadable Modules)
with command-line options for a total length of up to 63 characters.

Note to module programmers: each module here will be passed additional
command-line arguments to indicate how or why the user operation was invoked.

For the Reading Mail module, the 'which' value (in decimal) and the user-number
is passed (in decimal). Usually the user-number will be the current user logged
in, but not always (e.g. if the user is a sysop and reading other user's mail).
The 'which' values (defined in load/sbbsdefs.js) of MAIL_YOUR, MAIL_SENT,
and MAIL_ALL must be handled (MAIL_ANY won't be used).

For the Scan Posts module, the sub-board number and scan mode (both in decimal)
and the 'find' string (text being searched for) are passed as arguments
(in that order). The scan mode values (defined in sbbsdefs.js) are the same as
those supported by bbs.scan_posts(). All of the values should be supported
and they can be combined (e.g. SCAN_CONST|SCAN_NEW
and SCAN_NEW|SCAN_TOYOU). The 'find' string is only used if the SCAN_FIND mode
bit is set. It is the responsibilty of the module (if configured) to enforce
sub-board read access restrictions.

For the Scan Subs module, the first argument is 1 if "all subs" are being
scanned, 0 otherwise (normally the user is prompted for the breadth of the
scan in this case, but that's up to the module author), and the scan 'mode' is
passed in decimal, in that order. If the SCAN_FIND mode flag is passed in, this
module should prompt the user for the text string to search for. If this module
is not configured, the Scan Posts module will be executed for each sub-board
scanned.

Recursion protection was added, so it is actually possible for the Read Mail
module, for example, to call bbs.read_mail() and it'll work, but why would you?

If any of these user operations are initiated during logon, at the request of
Baja or JavaScript module, or whatever, and if the module is actually
configured (and not already executing to handle the operation), the module
will be executed in-place-of the built-in functionality. Feedback welcome,

by access_d.  Broken since v1.18 on Feb. 10th,  2015.

ID is a pointer on at least FreeBSD, cast to uintmax_t instead of DWORD.

scripts global scope (as opposed to js.global which is the instance global
scope), and having exit() define exit_code in js.scope instead of js.global.

This also sets exit_code in js.scope to null when preparing to execute a new
script.  If a new script starts in the same scope as an old one, the old
exit_code value will be destroyed.

This should only impact scripts where js.global != js.scope (bbs.exec()ed,
and mailsrvr)

(or by adding NOCIRCULARFWD to your sbbsecho.cfg):
When "Circular Path Detection" is enabled (the default), the old behavior was
to still forward the message to any links (if there are any), but not import
the circular/looped message (likely a dupe). Now, if you set this new option
to no (or add "NOCIRCULARFWD" to your sbbsecho.cfg), the message will be
completely ignored and not fowarded to any links (if there are any).
If you have no downlinks or you have circular path detection disabled, this
new option does nothing. The default is the old behavior (forward circular
messages).
Also updated the Toggle Options help text in echocfg (many options weren't
documented.

this read() call will block indefinitely. Fall-through to pseudo-random seeding
if read() fails. Fix for FozzTexx-reported problem on reddit.

hash entries will then have incorrect or invalid message numbers.

your return value anyway.

item enqueing stuff which has been carefully preserved and equally carefully
never used.

call free() when processing for a js_peek() call with the old manual
serialization.  Obviously, it hasn't been used since the update to the JS
internal serialization stuff, and the new fix doesn't need it.

js_peek() calls js_decode_value() which would free the data for successive
js_peek() or js_read() calls to choke on.

Thanks for the report MCMLXXIX!

into the wrapping bits since we've added a space.

their own line, instead, just break them at the end of the line and continue.

Also, fix a bug where the intended "check next character" test was actually
checking the last characer.

Finally, use a common slightly wrong word-length calculating function rather
than custom-rolled mildly wrong stuff in-line.

with the ability for the running program to override it, so stop calling
lf_expand() when EX_STDIO is set.  This makes the default scfg as a door
configuration work properly on *nix systems and shouldn't bork any existing
configs.

first.

of its startup structure.

list parameter valuie.

by msvc debug build and reported via assertion.

traversed.  The existance of the pnode variable implies this was the intent

that was crashing the last time I tried to use this feature.

SMB message header fields (msg_auxattr and msg_netattr), as requested by
AccessDenied, though most of these attribute flags are currently never set by
anything. <shrug>

defines XPDEV_THREAD_SAFE (not currently used in Windows builds) and
LINK_LIST_THREADSAFE (notice the inconsistent use of underscore :-)

defines XPDEV_THREAD_SAFE (not currently used in Windows builds) and
LINK_LIST_THREADSAFE (notice the inconsistent use of underscore :-)
Use of this property sheet fixes the problem with the terminal server global
variable 'uptime' getting corrupted when jsrt_GetNew() called listInit() from
js_rtpool.c which didn't #include sbbs.h and therefore had a different idea
about the size of link_list_t and thus corrupted the global data region
(zeroing out the 'uptime' variable, probably amonst other important things).

if time_t is unsigned and the current time is less than uptime.

There's comments that suggest the time(NULL) value is influenced by the
timezone, so possibly therre's a usage of it somewhere with the timezone
not being set comparing to an uptime that was set when timezone *was* set.
In this case, @UPTIME@ will say it's been up for zero days until the timezone
is set in that thread/process, or time(NULL) passes uptime.

the data/error.log.