This solves issue #817 for TLDR messages imported into DOVE-Net Tech Talk,
because those messages are imported via SMTP originally and thus have the
original (MIME/Q-encoded subject) in the message header (as RFC822SUBJECT).

For other messages with UTF-8 characters in their header fields (e.g. subject),
we'll need a different solution (Q-encode header fields that contain
non-ASCII chars on the fly), and then this solution could maybe be reverted.

GCC and Coverity (x 2) both flagged this one.

Properly read the index of the base, not of the base_code.
Fixes badly broken STATUS command.

Also, change the default smb_t.retry_delay from 250 to 100ms

Getting a lot of smb_locksmbhdr() failures with sbbs-Linux accessing message
bases (i.e. SYNCPROG in particular) on Samba share.

Similar to what I do with user.tab record locks 2 months ago, this will
extend the total shared/network file open attempt duration from about 5
seconds to about 45 seconds, but with incrementing back-off.

Trying to sbbs-Linux to run from a Samba share without file open/locking
errors.

Re-synced the sbbs_t version of nopen with the nopen.c version (wasn't
special-handling EDEADLOCK failures).

Mostly we're using fnopen() these days anyway, which doesn't have an sbbs_t
version (for logging warning messages about collisions), perhaps it should.

This date (basically 0) means either the dsts.ini file doesn't exist or there
was an issue reading it successfully (that was not detected by getstats()).

If this works, we can use it for EVERYTHING!
Baw ha ha!

Use sdl-config before falling back to the framework.
Move sdjclean into objodir and link with mt stuff.

Also fix last commit

So dos2unix 'em all.

When using MacPorts (and likely Homebrew), this isn't how this works.

New versions still support that.

This was a regression: Socket.recvline() used to not care what the timeout
duration was so long as there were bytes to receive.

Also, remove the ".0" from timeout values in documented mehtods that don't
(any longer) accept floating point timeout durations. We used to support
fractional seconds for some of these methods, and that was implied by using
the floating point default values, but that's no longer the case. poll()
still accepts a floating point timeout.

This was just a typo which didn't allow the single-file upload xfer prot menu
to be shown.

Actual fix for CID 11447 (previous attempt, commit f50c866f was
insufficient). Thank you Coverity!

It's slow and crufty, and there's a new mini on the block now.

Should fix OpenBSD builds.

It's super-picky.

Use standard isfinite() instead of never-standard finite()
Don't use -rpath-link on darwin (since it won't work anyway)

Rather than trying to back-port platform support, just grab the
latest libffi release and jelly it in.

Let's wee what the pipes tell us.

That's the key!

Ugh.

Otherwise, zero it out.  Most termios implementations don't put the
speed in here, but this *is* where dragons be.

This will likely fail though.

As noticed while trouble-shooting issue #813, calling comOpen() would
(on Linux, at least) set the port baud rate to 0 bps (B0) which in
most or all Linux serial drivers triggers special logic to deassert DTR and
RTS signals (to the modem, to attempt to "hangup" any connection).

If the app (e.g. sexpots) did not explictily set the port baud rate after
calling comOpen(), the port would be unusable. This is not how comOpen() works
on Windows.

So rather than just overwrite all the bits in termios.c_cflag, we clear the
fields we know we want to, set the bits we want, and leave the rest (which
usually includes the current baud rate, if CBAUD is defined) as-is.

Gracefully terminate with SIGQUIT, SIGINT, and SIGTERM

Ignore SIGHUP and SIGPIPE.

DDFileLister: When showing file info, check more of the properties to see if they exist first

See merge request !471

SDL_SetWindowSize() takes dimensions in imaginary units it makes up
so it can call something "Retina™".  SyncTERM however lovingly
crafts everything pixel by pixel for an atisanal ode to BBSing.

This change converts pixel sizes to Retina™ sizes before resizing
the window.  Should fix ticket 164.

I can't believe I missed this - this would've caused definite issues with file
transfers.

I saw a discussion in FSX MYS (between apam and GEARBOX)  which clued me into
their being an issue here. I do wish users of SexPOTS would report issues to
me. :-(

Incremented version to v2.1

Fix for issue #809