ESC[0;1;5;32;40m
Is shorter than:
ESC[0mESC[1mESC[5mESC[32mESC[40m
By about eight chars.

(wildcards supported: '?' and '*').

digits. This will reduce the liklihood of false-positive TG/RG pipe code
interpretation.

If the ringbuffer held more data than the linear buffer COULD hold,
both semaphores would end up clear, and the data would never be sent.

Fix is to not wait on the semaphore unless the ringbuffer isn't
"full enough"

To more-easily get the current sub-board or file directory internal code
(string). Deuce will test. :-)

ToDo: Check if TCP_MAXSEG actually *is* defined here ever.

Fix a (unlikely) bug when using chinked output with a full ringbuffer.

specified, if "filename.js" exists, it will be executed instead of
"filename.bin".
Previously, the ".bin" extension was always assumed if it wasn't specified on
the command-line. This modification allows exec/bullseye.js to take
precedence over exec/bullseye.bin without any change to the command-line
configuration. Execute "*filename.bin" if you want to specifically execute
"filename.bin" and not "filename.js" (if it exists).

FL_EXFIND mode bit is set. <sigh>

FL_FINDDESC mode bit is set.

enum constants (only used to map to strings) - this gives more flexibility in
error reporting (e.g. "ERROR - compiling JS script").

Then autotune the highwater mark to be the MSS and never send() a buffer
larger than that.

(trying to be consistent with post-as-verb, not noun).
Introduced bbs.list_msgs() for various listing (as opposed to scan/reading)
modes (text search, message to-you, etc.).

replaced sbbs_t::searchsub() and searchsub_toyou() with multi-function
sbbs_t::listsub().
Fixed some perceived bugs with SMB error reporting (popping the SMB stack
*before* reporting the error details).

restrictions into account (the 'D' and 'U' restrictions).

Updated JS docs for methods.

Updated JS docs for methods.

of numeric/statistical user fields:

* User.adjust_credits(count)
* User.adjust_minutes(count)
* User.posted_message([count=1])
* User.sent_email([count=1] [,feedback=false])
* User.uploaded_file(bytes [,files=1])
* User.downloaded_file(bytes [,files=1])

In the methods where "count" is optional (in square brackets), the default
value is '1'. So to increment the user's messages-posted statistcs by one
(for today and total), User.posted_message() is all that is needed.
Specifying a negative value allows adjust downwards (subtraction).
e.g. to remove 1000 credits: User.adjust_credits(-1000);

The User.stats properties are *intentionally* read-only (i.e. not a bug) since
there is no "safe" way to modify these properties using normal mathematical
operators (e.g. +=), hence the need for these new methods.

instead of user number (allow the higher level to determine what constitutes
feedback or not).

credits, and minutes - basically wrappers for adjustuserrec().

disable) user's spinning cursor setting.

Updated docs for methods with *optional* directory number/code argument.