Sent to terminal user after successfully sending netmail:
- InternetMailSent
- FidoNetMailSent
- QWKNetMailSent

As requested by Keyop in irc.

This should fix the recent JSDoor build issue introduced.

As pointed out by Keyop via irc, if the message has an attachment,
a comment is prompted for and since the "To:" prompt uses P_NOCRLF,
the first comment prompt was on the same line. So clear the screen, which
is what happens when the forwarded message has no attachment anyway.

JavaScriptOptions bit-field can be set in sbbs.ini and jsexec.ini to over-ride the default JS compiler options which have been changed from 0 to (options previously only used by JSDoor):
JIT | METHODJIT | COMPILE_N_GO | PROFILING

* JIT - TraceMonkey
* METHODJIT - JägerMonkey
* COMPILE_N_GO - compile-time scope chain resolution of consts
* PROFILING - Choose between TraceMonkey and JägerMonkey at compile-time based on profiling results

Other options available but not enabled by default:
* STRICT - warn on debious practice (i.e. similar to "use strict")
* WERROR - convert warnings to errors
* VAROBJFIX -  use last object on scope chain as the ECMA 'variables object'
* RELIMIT - Throw exception on any regular expression which backtracks more than n^3 times, where n is length of the input string
* ANONFUNFIX - Disallow function () {} in statement context per ECMA-262 Edition 3.
* METHODJIT_ALWAYS - Always whole-method JIT, don't tune at run-time.

Also:
- Fixed JS warning string formatting (missing space separator).
- Removed an extraneous new-line in lprintf() call in mailsrvr.
- Added basic assertEq() global method to jsexec, required when running SpiderMonkey test scripts.

The file attachments, when MIME-encoded, already include a MIME Content-type
header field, so don't send another. This should fix issue #233.

Fixes infinite mail loop.

So it actually looks like the *only* thing that doesn't expand
& strings is the output code.

This should also be handled by the game after a timeout...

Get rid of routineabort stuff and use the callstack thing.
Fixes ITEMEXIT

1) Comments do not start with a ;
   Any line that doesn't start with an @ is either a parameter to
   the last command (such as in @show), or is ignored.  Further,
   "extra" arguments are also ignored.  This means you can literally
   type comments almost anywhere.
2) There is a maximum "call stack" of two "frames".  If you nest
   subroutines three deep, the first one will never be returned to.
3) Implement @routineabort.
4) If @run is used in a subroutine, it acts as an immediate return
   The arguments are not consulted, and no error is displayed.
5) Of course, if you call subroutines three deep and return from
   two of them, the first subroutine is now the topmost frame, so
   run behaves normally there.

Since the filename is in the subject, we can't allow the user to change the subject (duh). Also, don't bother with the "Fwd:" prefix thing as that could potentially cause problems in other places where the filename (only) is assumed to be in the subject.

Also, make sure to create the destination directory when moving file attachments. These changes fix issue #230 reported by Keyop.

I noticed "DAILY ... Semaphore signaled" in the event thread log output. Now fixed.

show splash screen and await response before restoring system status. explicitly disconnect from json client when exiting.

Fixes issue in healers huts.

Documented here: https://pubs.opengroup.org/onlinepubs/009695399/functions/xsh_chap02_05.html#tag_02_05_01
This provides the best chance at read_raw() reading from the right
location and updating the file pointer as expected while avoiding
behaviour which is explicitly undefined by POSIX.

This allows more @whoison to be more accurate.
Also, fix a misplaced ) while I'm here.

(More issues with rape)

REF files need to set it manually if they want it.

1) ` vars which are always expanded.
2) & vars which are expanded "sometimes" (generally for display stuff).
3) "pure" vars which are only expanded when they are the entire string.

The main change here is in the & var handling... lw() no longer
expands these, so they can be displayed to the user... they are now
expanded in the following cases:

1) Anything that calculates the displayed length.  The assumption
   here is that the string will be passed to one of the following
   things.
2) Bar updates, either @quebar or @saybar
3) @do addlog
4) @do write
5) @moremap
6) @progname
7) @show
8) @writefile