This allows timing out the battle bit.  If the game/BBS crashes
while you're in battle, you should now only need to wait two times
the idle timeout (ie: 2 * 5 minutes) before you can get back in.

- In dorkit, start the timer if keyboard is invoked and
  dk.connection.active is false.
- In LORD2, check for a CONNECTION_CLOSED key after getkey() where
  appropriate.
- Also in LORD2, allow the busy flag to suspend pending timeouts.

1) Ciolib CIO_KEY_QUIT and CIO_KEY_MOUSE conflicted with ALT_7 and ALT_6
   respectively, change these to use \xE0 prefixes.
2) Add a new dorkit key "CONNECTION_CLOSED" which is returned by getkey()
   after the connection is closed.
3) Have the various connection back-ends send a CONNECTION_CLOSED key to
   the keyboard buffer when the connection is closed.
4) Have the local console send a CONNECTION_CLOSED key when the window
   is closed.
5) Disable auto_terminate in dorkit.
6) Introduce dk.connection.disconnect_timeout variable (defaults to 30
   seconds).  After a CONNECTION_CLOSED key is received, dorkit will
   immediately set js.terminated, then after disconnect_timeout seconds,
   will enable js.auto_terminate.
7) After a CONNECTION_CLOSED key, waitkey() always returns true, getkey()
   always returns a CONNECTION_CLOSED key, and getbyte() always returns
   undefined.
8) To prevent a poorly written door from hogging 100% CPU for the whole
   30 seconds, put an mswait(1) in the connection check when the
   inactivity timer is running.

This likely breaks things nobody does.

- Convert second argument to @readspecial to upper-case
- Convert both sides to strings for equality comparisons
- Implement @display label in file.name
- Fix @do XXX is getname ### where ### is the current player

By displaying "<DISABLED>" instead of the command-line in the event list.

It appears this was written for RTWall to detect BBS numbers with.

- Have getsvar() join arguments with spaces for strings
- Fix fg/bg in @readstring/@readnum
- Special-case NIL in readstring (this is where it's documented)

- Set default values for world.dat so it can be created with new()
- Add `r0 to start of the default more string
- Create the world file if it doesn't exist (for globals)
- Fix stupid error in @do trim
- Support all the different @clear commands
- Support the different @key commands properly
- Support @name command
- Only @say is still required for the NPC "stuff" that nothing uses
- Fix blank line skip looking for @begin after @if...then do
  Was looking for comments starting with ; only
- Add try/catch around maint call in case it doesn't exist
- Don't load rules.ref if there's a REF passed on command-line

Was broken the same way as Christopher Robin's House.

Previously dumped you on an uninitialized map, not returns you to the
hundred acre wood as intended.

In general, LORD2 ignores errors and continues, but various things
will cause exceptions to be thrown.  Instead of tracking all these
down and suppressing them, log them to error.log and continue.

Since we're doing this, we can now throw Error()s whenever we
detect an issue in REF files, so add some of these in.

See if this resolves rjwboys reported error:
threadwrap.h:204:42: error: expected expression before ‘do’
 #define protected_uint32_init(pval, val) atomic_init(pval, val)

Hope to address error reported by rjwboys via IRC when using
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
 from ansiterm.cpp:22   /user/include/c++/5/bits/c++0x_warning.h:32:2
error #error this file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options.

Calling @routine blew up the stack, so presumably this needs to be
done everywhere.

This excludes votes and polls automatically.

e.g. ANSI.SYS doesn't appear to support it

I'm not sure how long this has been like this, but the last_msg
of a sub-board can be a super high number (e.g. in the billions), so using
that value as the highest message offset would cause tons of message index
read failures and just cause this loop to interate unneccessarily through
tons of non-existent messages. Also, this code is utter crap.