GitLab

Curses mode does not allow you to control the mode.
This should fix mysterious and hard-to-pin-down UIFC MONO mode.

Curses mode does not allow you to control the mode.
This should fix mysterious and hard-to-pin-down UIFC MONO mode.

There are a number of conio changes in here too... too many to list.  Check
the diffs if you actually want to know what changed.

Add support for scroll "buttons" (buttons 4 and 5).

This likely breaks the forced mono thing.

They don't fix any problems, and likely nothing will use this code.

We don't need a unicode -> cpchar with ext...
We do need codepoint -> cpchar with and without ext.

This is planned to work with the built-in fonts... no real idea how to
make this work with dynamic fonts at this time.

We'll also need a line drawing set thing ala curses, but I'll worry about
that when/if I update uifc32 for unicode.

This is actually pretty terrible... people hate libraries that call
setlocale()... but I'm too lazy to update everything that uses ciolib,
so there you go.

compatible (most terms are these days).  In this case, curses mode works
correctly.

Add a new CIOLIB_MODE_CURSES_ASCII for the old behaviour.

Make resume only perform any actions if curses is suspended.
This may fix the Syncterm OS X raw on exit in -iC mode.
(But may not either)

Basically, this just tracks if curses is already suspended or not and if it
is, does not call noraw() and endwin() again.  This should fix the issue on
Linux since well-behaved scripts will call uifc.bail() before they exit.

It appears what's happening is that jsexec sets the terminal as raw, then
ciolib is initialized at which point ncurses saves the current terminal state.
Before exiting, jsexec sets the terminal back to cooked mode, then exits.
atexit() ciolib calls curs_suspend() which calls endwin() which restores
the previously saved terminal state (ie: raw).

Most of the copyright years in the source code were misleading (the date of
most recent publish was actually later) and all were unnecessary. I've been
removing copyright years piecemeal, for a long time, but I decided it was time
to just perform a bulk search and (mostly) replace. In some cases, I left
old copyright years on files that either are not used (and soon to be removed)
or obsolete and unlikely to ever be touched again (e.g. Win9x FOSSIL VXD). Some
of the runtime binaries still contain copyright years and those were updated to
2018.

Thanks scan-build!

The biggest impact is in the cterm =1n query, which is retaining 0 for
success and now uses 1 for all failures.

on explicit colors will do, use all 16 colors.

Also, if we have 16 or more colors, set CONIO_OPT_BRIGHT_BACKGROUND

This fixes bugs running syncterm -iC in syncterm.

Also, initial support for Win32 console palette setting.

Prevents arrow-key weirdness in SyncTERM (and presumably others).

and the OS X terminal displays unknown characters as '?', this resulted in
windows in curses mode on OS X system terminals having two icons... [?] and
[?].  One would give you help and the other would close the window.

This was clearly unacceptable.

As with mouse.h, this shouldn't be a separate header.

It doesn't make any sense by itself.

and does not cause a positive return from mouse_trywait()  This was
causing phantom mouse events.

Since mouse_pending() still returns the number of mouse events, use
mouse_trywait() in curs_cio.c to check if a mouse key is pending.

overridden.

NOT TESTED IN WIN32 CONSOLE MODE YET!!

can be properly handled.

after all!)