- date_format
- date_separator
- date_verbal
- birthdate_format

See JSDOCs for details

... make them more useful (e.g. when the result of script is a big string).

This will prevent the cursor from showing up when redrawing the
status bar, and implements feature request 79.

This isn't great, but it works (on FreeBSD)

It was at absolute max (an extra one and it would clip) which is
really a terrible thing to do to people wearing headphones.

I don't really need to do it this way, but the math for the different
wave forms depends heavily on integer wrapping (and WAVE_SHAPE_SINE_HARM
is just stupid).

Compile-time isn't the best time for configuration.

The first argument after the list was still being replaced.
Extended test to try the hard stuff.

This reverts commit ebe52737.

This reverts commit 4ce91537.

This reverts commit 33be8662.

We don't build on SunOS anymore, and using LD_RUN_PATH sucks.
Also, it was badly out of date.

Likely fixes difficulties pasting in SyncTERM.
Probably want to define some minimum amount you need to move to
trigger dragging.

The birthdate parsing is now a lot more robust and will recognize all kinds
of variants/formats and use range checks to disambiguate provided dates and
even support partial dates (e.g. year only, year/month and month/year).

The tests should all pass regardless of what the sysop has set for their
system date format in SCFG.

I had considered using sscanf() for the parsing logic but ended up going with
strtoul() only and that seems to be working well (as reflected by the passing
test cases).

... which is the format expected/required when entering or editing birthdates
in the terminal server. So this is a pretty embarassingly bad bug introduced
just before the v3.20b release to fix a less-severe bug with ecWeb new user
registration (still) writing 2-digit years to the user.birthdate field. :-(

Fix for issue #863

I considerd making these get_birthdate field functions more tolerant of less
strictly formatted strings (e.g. single-digit month or day), but decided to
keep this change to just a fix for the issue at hand. These functions could be
more robust to handle more variance in user/script input.

So they're auto-triaged in Synchronet.

Also, don't do stupid things if called more than once.

This allows a server that's being terminated to stop the port-bind delay/retry
loops and terminate more quickly in cases of port binding failures.

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

... 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