Also not happy with this one.

Log the error string if it's non-blank, as a warning (e.g. unrecognized
text.ini text.dat string ID).

Reduce the number of logged messages when config load failure happens.

Commonize the load_cfg() error log messages.

Displayed instead of hard-coded string in xtrn.cpp when attempting to run
16-bit DOS program on system with no DOS/DOSemu support.

Displaying these settings when they're not used can confuse sysops.

Biggest issue with this one is it doesn't allow BSD-style continuation
indentation, and forces aligning with parens.

This is almost, but not quite great.

The biggest issue where it falls over is in struct array indentation
and breaking.  It tries to force everything onto one line, making it
illegible. :(

Still not completely happy with it.

uncrustify nl_split_if_one_liner setting

Win64 builds were crashing decoding JPEG XLs on my AMD lappy.

... using uncrustify mod_paren_on_return config

White-space changes only, exception being the rare insertion of NL before
closing brace (couldn't find the option to disable that behavior).

I excluded some header files (e.g. sbbs.h) since uncrustify seemed to be doing
more harm than good there. I might just end up applying different set of rules
to .h files.

do_source_file: Parsing: sha1.c as language C
parse_cleanup(479): pc orig line is 257, orig col is 33, Text() is '}', type is BRACE_CLOSE
parse_cleanup(485): (frm.top().type + 1) is VBRACE_CLOSE
parse_cleanup(492): File: sha1.c, orig line is 257, orig col is 33, Error: Unexpected '}' for 'VBRACE_OPEN', which was on line 256

Causing uncrustify (0.80) to assert:

do_source_file: Parsing: execmisc.cpp as language CPP
parse_cleanup(479): pc orig line is 1257, orig col is 55, Text() is ')', type is PAREN_CLOSE
parse_cleanup(485): (frm.top().type + 1) is SQUARE_CLOSE
parse_cleanup(492): File: execmisc.cpp, orig line is 1257, orig col is 55, Error: Unexpected ')' for 'SQUARE_OPEN', which was on line 1257

Uncrustify-0.80.1-47-ba7fc1679

Some of these likely break WinCE support.

That *is* the write lock!

Don't go digging around in the filesystem when you don't have to.

Some Coverity issues, some deadlocks, some crashes...
Just misc stuff.

Also, we can now use a read lock.

(e.g. new user)

Similar bug fix as that just made to system.datestr()

Actually use the return value of datestr()

Fixes issue reported by Deuce, regression introduced in commit 490e86fa

"Scan for New Files since Never" is gibberish.

To fix jsdoor build

Helpful for scripts that want to know what file types (extensions) are
supported by the Archive class object.

Still need to work out the JSDOC support for this. Similar to the
Socket class object properties, this will have no documentation/description.

We need to set the "has pixels set" flag in both vmem and in the
bitmap_drawn array to prevent the update from erasing the pixels.

This is likely what the duplicated line was originally, then it got
broken when I switched to the vmem_cell_*() functions.