My first idea was to have a per-external-program setting to enable input
translation, but Deuce suggested it would be better done in input_thread() and
after some thought, I agree. Translations are not done in data/file transfer
mode, so use the CON_RAW_IN console flag to indicate this condition. So even
JS console.getbyte() will return a translated char unless the console is set
raw input mode (this could be surprising behavior for some!).

I considered saving/restoring the console mode when performing a file transfer
but will leave that to a time when obviously needed.

This fixes issue #497 in automatic way (no option needed).

Should fix curses-only build.

Pretty sure this is what intptr_t was created for.

Stupid 1-based coordinates.

e.g. when using Ctrl-K or when being prompted for key-press due to inactivity

A bare '\r' doesn't move the cursor to the first column in PETSCII terminals.
The '[' Ctrl-A code moves the cursor to the first column with multiple
cursor-left sequences, if necessary.

Ideally this sequence would be part of the text.dat string instead of
hard-coded here.

This fixes issue #561

Note, the CI job is needs to be updated with AS=mingw32-as... need
to find where that lives.

Instead, generate these as part of the build and use the .incbin
macro on GNU-compatible assemblers to build the .o file quickly.

No good solution for Win32, but genmap could write the C file again
and take forever building it if/when we need to build rgbmap.obj
on Win32.

Rename to ciolib_[ry]2[ry]ptr and put in ciolib.c/h
Should fix curses-only build.

One or both of these should fix weird GDI zombie issues.

If the codepage tables have holes where US-ASCII chars go, don't
send the character under the assumption that it won't be on the
keyboard (and certainly not in the "same" place).

Can prevent fall-through to curses from working.

There was a period of time when *nix installs of sbbs (after the
migration to Git) didn't include node2/3/4 directories (and thus
the node.cnf files in those directories). In such an install, report
the error converting those node.cnf files to node.ini equivalents,
but don't stop the upgrade to v3.20. The terminal server will fallback
to the firs node config if any other node config (node.ini) file is
missing, so that's still okay (though not ideal).

This fixes issue #560

Thanks for the report Bobrob!

Should fix auto-curses mode crash.

Create initial window at final size to avoid extra resize at start
- Load vmode before initializing the window
Track scaling whenever the X window is adjusted
Replace x11_window_height/x11_window_width with vstat.winwidth/vstat.winheight
Resize zim from init_mode_internal() to ensure it tracks current size on initial expose
Honour ciolib_initial_scaling
Check xim validity in local_draw_rect() in case of race
Add check to prevent divide-by-zero in handle_resize_event()
Use vstat for current on-screen info, and x_cvstat for desired info
- This allows using vstat.scaling in place of old_scaling
Have scaling set use a new mutex-protected variable
Fill in local_draw_rect() so we don't miss expose
Set max window size based on user area (or root window size if not available)
The WM Cyan uses may hate this...

This absolutely *must* fix the issue in SF ticket 103.

Should fix issue 103 on SourceForge (Black bars on X11 window)

This is now simple to implement.

Also, add ciolib_initial_scaling so the initial window can be created
with the appropriate scaling already applied.

We still need a way to specifiy the initial text mode, but these
globals are not the right way.