This makes ctrl/modopts/*.ini more useful for multiple language support

I accidentally committed an experimental x64 build configuration. I want to do
that right when I do add the x64 build configuration.

How these files differ from modopts.ini (and by extension,
ctrl/modopts.d/*.ini):

- The root section is always parsed, part of the returned object
- [sections] denote ARS that if matched (current user meets requirements)
  then those key/values are added as properties of the returned object
  possibly overriding previously defined properties (options), this allows
  different users (or clients/hosts, terminals) to get different option
  values much more easily

Up from the top row scrolls down, does not wrap to bottom.

Backspace from the top-left position scrolls down and moves the
cursor to end end of the new top line, does not wrap to bottom.

(so, [modname:charset=mode7], not [modname:charset=MODE7])

... cause it won't (fix directory case in path).

fexistcase() only corrects the case of the filename, not the directories in
the path. So we'll just use the lowercase version of the charset string,
always.

Also, return false upon failure of any call to replace_text(), not just the
last one.

This was the cause of some very slight funkiness when displaying files
after a save/restore (e.g. Ctrl-T or other global hot key) operation.

This is a getting a little kludgey

I think doing something with ARS would be nicer, but then we get into the
area of constructing a 'options' object out of keys from multiple sections
and which sections should supercede which? This'll do for now for Nelgin's
BBC mode7 terminal project.

For Nelgin's mode7 terminal project

No point in going any further and confusing users.

... in File.iniGetSections() method

because iniReadSectionList() doesn't recognize !include directives.

This fixes issue #871 whereby modopts.js couldn't find sections in
modopts.d/*.ini files.

I just want this in the history in case I ever want to play with
the concept again.

The fg/bg values all have multiple representations, and some bits
have extra meanings, so inequality there doesn't mean they're not
the same colour.

This fixes an issue where the *second* drag select on a screen
would not highlight blue backgrounds correctly.  The background
colour gets the "pixels set" bit flown because of how
restorescreen() works, which caused this to "know" it's not blue
and use a blue background.

A (good) argument could be made that savescreen()/restorescreen()
shouldn't result in any changes, but since uifc32 doesn't directly
use colours that aren't represented by legacy attributes, there's
no need for it to get tricky here.

SlyEdit: Display a user inactivity warning message (configurable)

See merge request !498

There's no need to set line = NULL since it's always overwritten.

Fix for issue #870

FF and VT both move down one line, scrolling if necessary.

The rest of the unsupported control characters have no effect
(ie: work like NUL)

Delete shows the delta.

Add ESC L and ESC M for insert/delete line.  Used by commando text.
Use a block cursor that blinks at 1Hz.
Discard invalid ESC codes.

Thanks Kirkman!

Address error report by Greg Meckel (THEICECA)
evnt QNET !ERROR 2 (No such file or directory) (EinError 2) in main.cpp line
3195 (event_thread) removing "C:\sbbs\data\VERT.qwk" access=0

... this could happen after a bad QWK packet was detected and renamed.

This allow language-specific module options

Completes feature request #95
Have fun kids!

DDMsgReader: Input timeout warning improvement - Now displays warning text. Also, new areYouThere configurable string in the theme file.

See merge request !496

DDMsgReader: Input timeout warning improvement - Now displays warning text. Also, new areYouThere configurable string in the theme file.

CTerm does not presently take any action for any of these, but it
does parse and ignore them.

<@Deuce> DigitalMan, also, as it turns out, Windows 7 was the last version of
Windows that supported processors without SSE2.

Since we're targeting Windows Vista and Windows 7 still, don't require FP
extensions that SBBS really won't get much benefit from anyway.

Resolves MSVC x64 build warnings.

Also fixes a bug with wrong sizeof argument used in readdir() (!)

I discovered the first case when FileBase.get_path() failed, but didn't
(immediately) throw an exception. Reviewing the other instances of
JS_RepoertError() calls found several that either reported a garbage (e.g.
NULL) string value or returned JS_TRUE.

The design pattern used a little in js_socket.c probably should be used more:

	if (JS_IsExceptionPending(cx))
		return JS_FALSE;
	return JS_TRUE;

... but that's more of a refactor than I had the stomach for right now.

It's Transfer-Encoding:, not Content-Transfer-Encoding:, and each
chunk has a \r\n appended to it.

With the latest change, *val will be \n after the last item, so
this avoids an extra loop through the loops.