- don't indent keys
- separate sections with a blank line (to improve readability without idents)

A nice tip from Ragnarok (DOCKSUD)!

Version 1.29: When reading a message, if a message is written to the current user, the 'To' username in the header above the message is now written in a different color.  Also, there are new color settings available in the theme configuration file (see the readme for descriptions): msgHdrMsgNumColor, msgHdrFromColor, msgHdrToColor, msgHdrToUserColor, msgHdrSubjColor, msgHdrDateColor

It seems we don't actually close() remote sockets, we let the destructor
do that.

Also, log it when it's changed.

- msg() now returns an int (e.g. 0 for OK, non-zero otherwise)
- add msgf() a printf-style version of msg()
- add confirm() a printf-stle yes/no dialog (returns TRUE on "Yes"/default)
- add deny() a printf-style no/yes dialog (returns TRUE on "No"/default)
- add yesNoOpts to allow application to over-ride "Yes"/"No" strings.

files were external to the executable (to conserve that precious 640KB of RAM!)
Some more use of SAFEPRINTF for good mesaure.

Use the COPYRIGHT_NOTICE macro rather than the build year.

This may be the root cause of the extended netsplits we've been seeing.

with iniReadFile() has one or more !include directives.
!include directives must be followed by a space now so we don't false-match
!includenotrightnowthankyouverymuch

Win32 can no longer exit() and WinExec() itself with impunity.

White-space fix-ups in header file.

- eval_first = a JavaScript expression to execute (almost) first thing
- eval_last = a JavaScript expression to execute as the last thing

"up"

New per-file properties supported:
- ars: access requirement string
- tail: print (view) the last n-lines of a text file rather than entire file
- mode: override P_mode flags (default is now P_OPENCLOSE | P_CPM_EOF)

The 'E' opertor command allows each file description to be edited too.

This means I needed to whip up utf-8 <-> cp437 converters.

Only loss of functionality is that we can't paste NULs anymore.  We can
*copy* them though, they are converted to zero-width non-breaking spaces.

Depending on feedback, I may need to normalize the UTF-8 before conversion
to get the most matches, and zero-width/combining codepoints should likely
be stripped instead of replaced, but I'm not overly worried about it.