Not all implementations set POLLHUP when a TCP socket is half-closed.

Was returning disconnected when it wasn't at times.

This likely unbreaks the things.

A socket isn't bad just because there was no incoming connections. :D

This won't impact Synchronet as it has a separate signal handling
thread, but we still need to behave properly for processes that
don't.  I'm also saying that ENOMEM does not indicate a disconnection,
though it may be better to pretend it was disconnected...

socket_readable() returns TRUE if recv() will not block if called
on the specified socket.

socket_writable() returns TRUE if send() will not block if called
on the specified socket.

socket_recvdone() returns TRUE if all data has been recv()ed an
the socket is closed.

"will not block" includes "will return an error".

This matches the three main use-cases for select() of a single socket
in Synchronet.

Use them in the SyncTERM RLogin stuff so they can be tested easily.

MinGW32 is getting long in the tooth and is missing a lot of modern
Windows features as well as having broken headers.  Most people will
be using MinGW-w64 at this point, so add support for it.  Once I
ensure SyncTERM works properly with it, MinGW32 support will be
discontinued.

I suspect this will impact exactly zero people since the reason this
exists is to build the Win32 versions of SyncTERM on FreeBSD.

Changes:
- Explicitly request 32-bit Windows output
- Detect the string "mingw32" anywhere in the hardware description
- Explicitly link with libuuid
- Add a terrible hack to syncterm.c to block wincrypt.h

Do not clear at the current X/Y on scroll (derp)

Scrolling would clear the line to the end of the screen, not the
end of the scrolling region.

Sorry echicken.

Could be useful for knowing if you need to increase MaxClients for typical
usage.

First look for a linked node matching the node address string as passed,
then look for a match using the normalized address (removing .0 and @domain).
The "ALL" wildcard should not be used for password lookups.

This should fix reported issue 240.

Borland hates it.

There has been a sighting of Synchronet exceeding FD_SETSIZE sockets.
This means select() is of less use and we need to start migrating to
either poll() or platform-specific methods to achieve the same end.

This commit is mostly to check that poll() builds on Win32 and that
it actually works.

Hopefully fixes crash in lord when composing a message and using
word-wrap.

There's a comment saying we set key=0 when we consume it... do so
in a couple cases where it wasn't done.

Range check the key before sending to the remote.

This should not actually do anything different, but in the future
if things are changed at least the comments won't be misleading.

This is pretty insane since SDL2 completely ignores the keysym value
of the X11 keyboard event, so here's what we do...

1) When there's a keypress that includes right-alt, store the sym/mod
2) When we get text input, if it's the same as we would get if ALT
   wasn't pressed for the last keydown, parse through the mapping
   (ie: handle ALT keys)
3) If it's different, use that (gets AltGr modified value)

I get that AltGr is hard in a cross-platform way, but just pretending
it doesn't exist at all for key input is a very weird choice.

Caused a SyncTERM hang if it played a FG beep.

Thanks Mr. Executive Chicken esq. for the telephone call and bug report.

2 new configuration params: MaxLogSize (default: 10M) and MaxLogsKept (10)

error: ‘handle_mutex’ undeclared

This reverts commit 6a4fbf28.

This allows the playback thread to open the device and errors to
be checked.  Otherwise, the first sound won't play.

1) user.number immediately after login() remains zero, but changes
   "sometime" after.  Avoid using user.number right after login()
   call to generate filename.  All data/user/0000.imap files can
   be deleted after this change.
2) Saving Seen data would modify the object storing it when binary
   seen values were used.  Use JSON.parse(JSON.stringify() to make
   a copy before saving and restore it afterward.  Should fix issue
   reported by nickshanks1 over IRC.