You can now use CSI [ 38 ; 5 ; X m to set the foreground colour, and
CSI [ 48 ; 5 ; X m to set the background colour from the palette and use
any of the 256 standard colours, any of the 16 Commodore 64 colours (start
at 256), or the two Atari colors (after the C64 colours).  In addition,
you can use the palette redefinition commands to extend the palette past
those entries.

NOTE: Since this is only CTerm so far, using SyncTERM and UIFC features
will lose the palette blocks for the characters, and they will revert to
their current 16-color value.  Further, I haven't testing how this interacts
with alternat fonts, blinking, etc yet.

But it looks cool!

(fg and bg) for the given attribute.

Switch cterm to using ccputs() (which has no implementations yet).

Also, remove the magic "Don't use the palette" value.

1) Fix last commit.  Crashes/Video corruption resolved.
2) Add ccputs() and cputch() to ciolib.  These take a colour value as their
   first argument, which is a palette entry.  They otherwise work the same
   as their counterpart without the c prefix.
3) Add a flags member to vstat which needs to be set before loading a mode.
   The only defined flag is currently VIDMODES_FLAG_PALETTE_VMEM.
4) If VIDMODES_FLAG_PALETTE_VMEM is set, allocate 32-bit arrays for the
   foreground and background palette entries for each cell.
5) Have bitmap_con.c use the palette vmem flag.
6) Have movetext() copy the palette entries along with the regular vmem.

In theory now, bitmap_con.c will handle giant colour palettes, and anything
that uses movetext() (ie: scrolling) will maintain the colours.

gettext() and puttext() unfortunately can not access the palette memory...
we'll see if we need extended replacements for them or not.

finish work.

This is going to be cool though.  Don't try this at home unless you're me.

term.c:2156:17: warning: operation on ‘cterm->log’ may be undefined [-Wsequence-point]
       cterm->log=cterm->log |= CTERM_LOG_PAUSED;

Also, delineate standard from non-standard.

QWK kludge lines - string literals should not be interpretted in these
strings! Yes, you'll need to cvs-update xpdev/* too.

values (string literals not supported/parsed).
iniPopKey() no longer supportes string literals. Use the new iniPopString() if
you need to pop parsed string-literals from a string list.
All the non-String get/read function no longer bother with parsing string
literals.

Instead of each control function having separate code to parse sequences,
use shared code which splits it into a structure and parses parameters.

This fixes all sorts of ANSI bugs with leading zeros, default values, etc.

Not all sequences have been updated yet, but I'll plug away at this slowly.

Now, instead of a couple sequences having broken parsing, and them all being
broken in different ways, all sequences can be broken in the same way all at
once.

Use C64 palette from CTerm
Switch drawrect to use 32-bit pixels
Put the colour palette index into the screen array, not the attribute palette one
Remove dac_colors from video_stat structure

bitmap_setvideoflags() force a screen redraw.  This fixes the status bar
in SyncTERM after a CSI 32 h / CSI 32 l pair.

no responses were being sent for a couple of different reasons (misplaced break
and erroneous check of strcmp result).

CTerm (and therefore SyncTERM 1.0) required an extra two ignored garbage
bytes in the font data.

ESC ] 104 ESC \ will reset all palette entries.
ESC ] 104;X;Y... ESC \ will reset specified palette entries only.

ie: perl -e 'print "\e]104;1;2\e\\"'
Will reset palette entries 1 and 2.

ESC ] <string> ESC \

Where string is in the format:
rgb:R/G/B
And the values of R, G, and B are one to four hex digits.  For example:
"\e]4;1;rgb:0/0/a8" will reset the blue entry to the default value.