e.g. running '../cleanall.sh' from the src/sbbs3 dir

As reported by GCC 10.2 with FORTIFY=1 and SANITIZE=1

Not sure how I missed this before <shrug>

This should fix the SBBS-MSVC build in CI.

This utility doesn't expand Ctrl-A codes, so just strip them.

The InactivityAlert string is sent as a warning before disconnect when a
visible alert (AreYouThere) shouldn't be sent. Defaults to 3 beeps.

Remove the content of the NodeActionMultiChat (over-rides the hard-coded
default node status) - weird that this was the only node status that reported
the user's security level in the default configuration. This has been this
way since sbbs v2.30, at least. I think it was to be sure that others could
see the age/gender of those they were chatting with. But we have other methods
of reporting that in node status now, so we don't need to use this override
string to accomplish that.

This reverts commit a8e1ff3e.

It turns out neither platform this targeted actually set that
variable correctly.

It appears that XDG_ENVIRONMENT_TYPE will always equal "wayland"
when XWayland is in use, so when we see that, switch to CLIPBOARD
instead of PRIMARY.  This should fix WSL and ChromeOS, and be
irritating on GNOME, so it's a win all around.

The directories of the *first* library was always the target of the (new)
"Clone Settings" option. We're using a dir_t for each lib's dir_defaults, but
that doesn't mean the dir_defaults.lib is initialized to a correct libnum
(it's not), so don't use it.

Still be sure to check the return value of write() though.

The return value of x11_event() isn't actually checked anywhere currently, but
still Deuce might want to adjust the new return value here (__LINE__ or -1?).

Some indicental trailing whitespace was auto-cleaned up part of this commit.
Unexpected as I thought this code had been uncrustified already.

Should use safe_strerror() here instead... later.

Fixes recent regression with scfg

nopen.c:37:15: runtime error: left shift of 1 by 31 places cannot be
 represented in type 'int'
nopen.c:39:18: runtime error: left shift of 1 by 31 places cannot be
 represented in type 'int'
userdat.c:251:111: runtime error: left shift of 1 by 31 places cannot be
 represented in type 'int'

There are lot of 1<<31 macro definitions in this repo, so I'm expecting a
lot more of this type of fix to be required to make UBSan happy.

e.g. runtime error: store to misaligned address 0x7ffec33195e3 for type
'short int', which requires 2 byte alignment

These aren't a problem for x86, but could be a problem for some other CPU
architectures that don't support unaligned access. I didn't use memcpy() to
resolve this (though that would've worked) to make this change endian agnostic.

... declared with attribute ‘warn_unused_result’

the hash lib dependency was missing

scfgsys.c: In function ‘edit_sys_delmsg_policy’:
scfgsys.c:498:3: error: case label does not reduce to an integer constant
  498 |   case SM_USRVDELM | SM_SYSVDELM:
scfgsys.c:504:3: error: case label does not reduce to an integer constant
  504 |   case SM_SYSVDELM:

No obvious bug fixes here, just future proofing.

New issue as result signed int total_dirs (increased from uint16_t).

Because bitmap_get_scaled_win_size() was being clamped to maxsize,
no matter how much mult was incremented, w and h would never be
larger than maxwidth/maxheight and only under exceptional
circumstances would the be equal, which would result in an infinite
loop.

While we're here, set the integer scaling value so we're not chasing
ulps all over the place with floating point math/scaling when we
don't need to.

None of these were even theoretically possible on any platform, but
I took the opportunity to add bounds checking to bitmap_puttext(),
so that's good I guess.

Add some malloc() return checks, comment fall-throughs, and resolve
a sleep while holding lock.

None of these should actually matter, so hopefully I didn't add a
new bug.

This allows the ANSI yellow colour to be yellow instead of the
brown used in IBM CGA monitors.

- Support LCF (Last Column Flag) mode per DEC STD-070
  (Despite years of protest that it's stupid)
- "Properly" support CSI 7 m and CSI 27 m
  Now, when in "Negative Image" mode, changes to the foreground
  change how the background is drawn and vice-versa.  Perviously
  this command just swapped the two values and called it good.

Adding and removing typecasts and changing some types (of ints).

So Clang-FreeBSD was warning (in compiles of scfg/scfg*.c by Deuce):
result of comparison of constant 100000 with expression of type 'uint16_t'
(aka 'unsigned short') is always true

Why? Cause a uint16_t's max value is 65535 (less than 100000). Sure we could
have just lowered the UIFC max number of config items to 65535, but that would
have been too easy. And why are these compared-with values of type uint16_t to
begin with? Because most ctrl/*.cnf lists (of configuration items) were
limited to 65535 entries cause ... 16-bit DOS, historically. Now that *.cnf
files aren't used, we could just increase these scfg_t.*_total type sizes from
16 to 32-bits, yeah? The result is this commit.

I went to (signed) int so we could still keep -1 as the special illegal
sub/dir num value (e.g. INVALID_SUB, which is sometimes used to indicate the
email message base). Theoretically, 2 billion configuration items could be
supported in these lists, but SCFG will limit you to 100000 anyway. So there's
a whole lot of s/uint/int in this commit.

I'd be very surprised if this doesn't result in some new GCC/Clang warnings,
but at least the old "comparison of constant 100000" warnings are now gone!

Fix bad and poor unicode mappings, add support for sending Insert
and Pipe.

Toggled using backtick.
Current state is shown in the status bar.

Since we previously couldn't actually *show* the status bar in
ATASCII (or C64) mode, enable that as well.  This means supporting
40-column status bars too.

We still default status bar to off for those modes, because that's
likely what people actually want.

Also, it seems ENTER was broken in ATASCII mode, so fix that as well.
Implements SF feature 61