The option from the menu (ALT-Z/CTRL-S) was copy/pasted years ago
and never updated while the keyboard shortcut (ALT-L) was updated
quite a bit.

This extracts the ALT-L code into a function and calls it from the
menu.

This should fix the recent issue when a larger or smaller version
is painted inside the window after resize, as well as fix ALT-→
when the current size is not an integer multiple.

This is my happy place on the desktop system running xfce4... any
higher, and it interferes with how I manage my windows.

Hopefully, this value convers the initialization portion perfectly
on all systems (hah!).

Instead of strictly using "first resize", also count flushes and
assume the hack isn't needed after five.  Experimentation on my
ChromeBook shows 3 to be sufficient, so I'm sing five for now.

Odds are that this will still mess with tiling WMs, but I don't use
one, so I don't mind yet.  I expect this will be better, but likely
still not great.

Fixes issue with possible corrupt display when "weird" scaling
changes occured.

Bugfis:   Be sure to terminate value if returning deflt.
Paranoia: Terminate value if iniGetString() returns NULL

I think the only way to trigger the paranoia is to pass NULL as the
default when reading a key that's not present.

The first time we receive a MapNotify or ConfigureNotify that sets
the width and height, resize the window instead of accepting the
current window size.

Silly to pass a 728-byte object as a parameter.

No more using the standard int type and having it work.
Thanks Microsoft.

Use strtoll() to parse number (except when _BORLANDC_ of course)

OpenFile() returns HFILE and is sus, CreateFile() is more complex,
but returns a HANDLE (and is what MSDN suggests I use).

This is why I returned ret. :D

Fix incorrect Coverity issue that speculates this may return fval.

This was the behavior for all string input in SBBS until recently
(Commit 5dec1519), with this change, an exception is being
made for message subjects, but the vast majority of other string
input is still limited to single-byte (i.e. US-ASCII or CP437)
characters.

This should fix issue #720

The first fix was to copy the right value, the second fix was to
ensure zero-length strings are terminated.

Also, fix macro name collision with GetDiskFreeSpaceEx

There's still outstanding issues in Coverity around sftp_state and
sftp_channel that need some deep thought, but this one is trivial.

Prevents buffer overlow with manually edited or corrupted files.