The created message queue for each background-load()ed script was never
detached-from by the child thread, so the linked-lists (and their semaphores)
were never freed. Calling msgQueueDetach() before ending the background_thread
fixes that leak.

to TRUE meant the FILE* (created with fdopen) would never be closed. So we now
duplicate the file descriptor and get rid of the external flag, always closing
Files (FILE streams) upon File object finalize.
This fixes the resource leak leading to the eventual "Error 24 opening ..." in
the ircd.js when loaded via jsexec, on Windows. This error happened after
169 calls to load(true,...), because each background load creates 3 Files
(for stdin/out/err) and those FILE streams were never closed/freed, and
169 * 3 = 507, plus a few open files = 512, the maximum number of open file
streams in the Microsoft CRTL apparently. Thanks to Deuce for recognizing these
numbers as "magic" and pointing to the likely cause.

"4294967295 File closed"
"0000 File closed: /path/to/file"

If an incoming message contains no CHRS/CHARSET control line *and* the message
text contains valid UTF-8 character encodings, set the FTN charset value to
UTF-8 so the message will be displayed/handled accordingly.
I did not add checks for header fields (to/from/subject) - we should probably
auto-detect UTF-8 in those as well, but for now, I don't see messages coming
into FidoNet echoes with UTF-8 in the header fields.
Incremented SBBSecho/EchoCfg version to 3.10.

This only impacts the new socket_select() method with multiple arrays.

Instead, just return -1 from js_socket_recv().

crashes jsexec (for now).

Thanks Razor.

Version 1.27 - Bug fix: Now displays the message score in the header even if the message only has downvotes

if present in the cfg file, newslink will send an RFC 2980/3977 compliant
"MODE READER" command before authenticating with the news server. Some news
servers require this command be sent by the client before supporting so-called
"reader commands", like "GROUP". See
https://mail.python.org/pipermail/mailman-users/1999-October/002396.html
for an example.

Thanks, EC.

If you want to use the server, delete the semicolon.

blessed among warrior -> blessed among warriors

apostrophes
last birthday before disappeared -> last birthday before she disappeared

Version 1.26: Fixes a bug that was causing some of the message vote tally information to be displayed as "undefined"

and don't let's forget about our friend the apostrophe,
nor overuse him neither.

It sucks.

Hopfully this doesn't break the Borland or Watcom (?!) builds.

terrible and has been fixed.

it's a CP437 character (e.g. inadvertently included in a UTF-8 encoded text)
and display as such.

line too. The 0xFE (CP437 block) character is not a valid UTF-8 character
sequence.

function for external sockets.  However, service thrads that use TLS were
relying on the finalize function to clean up the TLS session.

Revert 1.242, and add a finalize parameter to do_js_close() which will only
avoid the shutdown() call rather than completely avoid do_js_close()
completely.

This fixes a TLS session leak that would eventually prevent any new
encrypted connections.

name. This is a fix for "From", but "To" and "CC" header fields would need
a similar fix (not included in this commit).

4.07 appears to be where trainers.dat was introduced, and the strings
in there supported LADY variables.

I don't want to support LADY variables, but Aladdin has always mentioned
your weapon, so replace &PWE in needstr1 with the current weapon name.

NaN NaN NaN NaN
String Input
Goodbye.

Fix typo in GetForestGold.