Since SYMLINK=1 is valid/suggested for install/GNUmakefile, this is a common
mistake that we can catch here.

'T' command from the reading messages (O)perator menu

Abstraction the twit-list usage.

The user name is better to log than the user number. Include user name in
brackets.

Colons are not legal filename characters on Windows and when virtual hosts are
enabled, the IPv6 address of the server may be used in the access-log filename
so we need to clean that up or errors opening/creating the access-log files
occur.

"HTTP Logging" replaced in log messages with "Web Server access-logging".

Using new FCLOSE_OPEN_FILE macro to close and NULify open FILE*'s.

Change CLOSE_OPEN_FILE to a do/while(0) to eliminate extraneous semicolon

The first write to a the temporary SBBS_SSJS.*.html file will open the file.
This should reduce the number of 0-byte files left laying around in the the
temp directory, which shouldn't be happening in the first place.

Also:
Fixed bug noticed in temp file clean up loop:  POST data files would *also*
be retained when the DEBUG_SSJS option flag is set.

Also:
Replace some unsafe string operations with safe equivalents.

Happy Thanksgiving Nelgin!

Default: Warning

I'm tired of SSH-related errors that I can't do anything about, filling
my error.log file and mail inbox.

error: expected ‘)’ before string constant

Harumph.

std::atomic's need to be brace-initialized, or else we fail with
"use of deleted function" errors

Odd that MSVC built it just fine.

Include function names. Include host:port in "Unable to connect" error.

And other safety improvements in getsub()

getkeys() could return -1 if user disconnects (and SS_ABORT not set), so this
appears to be a valid bug.

Add comment/question about the use of JS_SetReservedSlot(), for Deuce

getkeys() is actually never (currently) called with a NULL arg, so this
could not actually occur, but better to prepare for that eventuality.

This looks like a case of not following the YAGNI principle.

Unlikely, but valid thread-safety concerns by Coverity

In response to Nelgin's inquiry:
DigitalMan would it be difficult to add login/logoff date/time to these
messages?
Node  2: xxuserxx logged on Telnet
Node  2: xxuserxx  logged off

Now, you can just use @-codes to add that kind of thing to these text.dat
strings.

Ideally, this would use startup.tls_error_level, but which one? And how?

Also, make a TODO comment to fix the fact that all JS Socket log messages
are logged to the terminal server log output. :-(

Saves some opening, reading, and logging, but otherwise was harmeless.

Fix issue #422

Seriously though, this doesn't always do the same thing as outputting a '\n'
(e.g. in PETSCII mode, it sends a "cursor down" (17) control character).

Also use sbbs_t::newline() as the underlying implementation of
console.newline() rather than a hard-coded CR/LF output loop.

Added new console methods:
	cond_newline() - equivalent of Ctrl-A/
	cond_blankline() - equivlaent of Ctrl-A?
	cond_contline() - equivalent of Ctrl-A\

... so a JS script author doesn't have to output Ctrl-A codes to invoke those
functions.

To enable a server that's disabled in the sbbs.ini file, just use the <server>+
option (e.g. 't+' to enable the terminal server). To run *only* that server
(and no other servers), use the '<server>!' option (e.g. 'w!' to run *only* the
web server).

js_init() failures are now logged with a critical error level (instead of just
"error").

js_execxtrn() now returns -1 if a JS context can't be created. This eliminates
redundant error messages from calling js_execfile with a NULL context.

Replaced _property_ver_list (array of numbers) with _property_ver_list (array
of objects) with a "ver" and (optional) "desc" property. This solves the
enumeration order problem with objects that have both manual and table-based
properties. Object's property tables (arrays of jsSyncPropertySpec) can now
(optionally) contain the property descriptions. For properties defined in this
manner, there will never be another mismatch between ther name/type and
description/version in the jsobjs.html (a problem has re-occurred several
times through the years with nebulous work-arounds).

We still use _property_desc_list arrays for additional (e.g. manually defined)
properties in such objects or just objects that only use one method of
property definition and are not subject to the enumeration order problem.

Fixed numerous typos.

Using more consistent terminology and HTML mark-up.

Some beautification and enhancement of readability, but nothing too major.

We don't need the carriage returns and they cause Git warnings:
warning: in the working copy of 'src/sbbs3/text.h', CRLF will be replaced by LF the next time Git touches it