backspace/delete key prompt, set the PETSCII flag in the autoterm *and* the
user's setting. If a CBM/PETSCII user actually got that prompt, that means
they were probably connecting to the wrong TCP port in the first place, so
relying on auto-terminal won't work for them on subsequent connections. We
probably should have a way to manually turn off/on PETSCII support, when
needed. <sigh>

^U, ^P, ^T, ^K, etc. and not 0. This allows a CBM/PETSCII terminal user
to actual hit their Backspace/Delete key (^T) in response to the new new-user
prompt

- turn off the user.misc PETSCII flag (too)
- don't copy the current autoterm flags into user.misc - this should no longer
  be necessary since the correct way to detect current terminal capabiilites
  is via calls to term_supports().

- "lsaquo" and "rsaquo" (angled versions of "lsquo" and "rsquo")
- "zwj" and "znnj" (zero-width joiner / non-joiner)

can't because it's a DOS program and the current node doesn't support it.

(when/what is executed, or at least attempted).

to a text/html part of a multi-part MIME encoded message if no text/plain part
exists.
Changed smbmsg_t.charset to smbmsg_t.text_charset.
Added smbmsg_t.text_subtype (e.g. "plain" or "html").
Fixed issue with parsing parsed plain-text when the charset was the last
element of the MIME-part header.
MIMEDecodedPlainTextFmt text.dat line now includes the text sub-type arg

when set, force a clear-to-end-of-line sequence to be sent to the remote
terminal before sending a carriage-return (CR, '\r') character. This is useful
in scenarios where you want to move/home the cursor and *not* clear the screen
and then display or execute something that assumes clean lines are being
displayed on and thus wouldn'd bother with any clear-to-eol sequences before
line-endings.
Any scripts that enable this mode should disable it upon exit (e.g. using
js.on_exit() to restore the original console status).

JS's console.getkeys(). If no mode value is specified, K_UPPER is the default
behavior (same as before). *.getkeys() currently only recognizes the following
mode flags:
- K_UPPER
- K_NOECHO
- K_NOCRLF

K_NONE (0) is also a valid value.

declaration

MSVC had no problem with this. <sigh>

Use this in place of JS_GetPrivate() in native class methods that need the
class instance's private data pointer and will do bad things if that pointer
points to something other than what is expected. mcmlxxix (matt) discovered
that using Object.apply(), you can invoke class methods where the 'this'
instance is a different class. This would result in
"Internal Error: No Private Data." or a crash.
So now, gracefully detect this condition and report a meaningful error:
"'<class-name>' instance: No Private Data or Class Mismatch"

Also, important to note: if the method uses JS_THIS_OBJECT to get the JSObject*
to pass to JS_Get*Private, then it must do this *before* it calls JS_SET_RVAL.

From jsapi.h:
 * NB: there is an anti-dependency between JS_CALLEE and JS_SET_RVAL: native
 * methods that may inspect their callee must defer setting their return value
 * until after any such possible inspection. Otherwise the return value will be
 * inspected instead of the callee function object.

The js_crypt*.c files still need this treatment.

the 'keys' argument is optional. If no keys are specified (or NULL), then any/
all non-numeric keys are considered valid input and may be returned by this
function/method.

as well as the auxattr "Attach" when either FILEATTACH or MIMEATTACH is set
(requires an updated MsgAttr line in text.dat).

I know... this list of %s's was a bad idea to begin with, but oh well.

after sending via POP3 (the MSG_READ attribute flag is already indicating that).

- votes
- priority
- delivery_attempts

headers).
Don't reference the (currently unused) times_downloaded and last_downloaded
msghdr_t elements/properties.
Set the current node action value *before* calling the scanposts_mod
("Scan Msgs module") in sbbs_t::scanposts().

Expanded codes will not *not* go beyond the terminal column width (minus 1).
If you need the old/wrap behavior, add a "-W" modifier to your @-code.
If a length value is specified with -W, it is ignored.

- MSG_TO, MSG_FROM, MSG_SUBJECT now reflect the header values passed
  to sbbs_t::show_msghdr(), JS bbs.show_msg_header() and not necessarily the
  actual stored (e.g. MIME-encoded) header values.

New codes:
- MSG_CC - reflect a message's CC list, if it has one
- DATETIMEZONE - combines DATETIME and TIMEZONE in one string

used to display a CC list, when applicable.

"read mail" module is executed, so that the node action is correct more often.

show_msghdr(), over-riding the values from the passed smbmsg_t. This is useful
for, say, displaying MIME-decoded values rather than the MIME-encoded versions
of the header fields that you often find in email today.

Copy the upvotes, downvotes, and total_votes to the smbmsg_t, replicating
what is done in sbbs_t::scanposts() - these are used by sbbs_t::show_msghdr()
so we need to copy them if we're going to be replicating that functionality
(showing up/down votes and score) in message headers shown with bbs.show_msg()
and bbs.show_msg_header().

angle brackets in the "RCPT TO" command sent to the SMTP server. This is an old
bug but now appears because we are now (recently) actually storing the SMTP
forward-path in the message header.

settings affect both NetMail and EchoMail import/export.

Renamed MIMEDecodedPlainText to MIMEDecodedPlainTextFmt
(since it is now a printf-style format string).
No special handling of non US-ASCII (e.g. UTF-8) characters... yet.

- mime_version (from the message header, if MIME)
- content_type (from the messgae header, if MIME)
- charset (from the plain-text MIME portion content-type header field)

(when set to Yes).

The default is off (no stripping). Previously, Soft-CRs were always stripped,
but this behavior is now seen as an anachronism as CP437 char 141 is an
important non-English laguage character and used as such in FidoNet msgs.

in switch

nicely when displaying at various terminal widths.

For QuickBBS editors, the default will be the same as previous behavior: to
convert Soft-CRs to Hard-CRs (CRLFs).
For non-QuickBBS editors, the default will be to treat Soft-CRs as any other
valid printable character in the text ("Retain").
A 3rd option is available to strip Soft-CRs completely from the generated
message text.

For QuickBBS editors, the default will be the same as previous behavior: to
convert Soft-CRs to Hard-CRs (CRLFs).
For non-QuickBBS editors, the default will be to treat Soft-CRs as any other
valid printable character in the text ("Retain").
A 3rd option is available to strip Soft-CRs completely from the generated
message text.