alphabetized, so the indexes don't necessarily match the order (of timed
events) in SCFG.

text.
Use strcasestr() for message body/header-field text searches (simplify
the code) - not sure why we needed strip_ctrl(), so removed.

the tags (no yes/no prompt), and use the original message's tags as the
default value.

MSG_SUMMARY is currently never populated by anything.
MSG_TAGS is a new (optional) thing.

from both ends of the input string automatically and disallow (ignore)
more than one consecutive space character mid-string.
The returned value is still the non-trimmed string length - perhaps that
should be changed.

a message header.
Added "tags" and "summary" (previously missing) to the property fields
parsed when adding/writing a message header. This parse code is getting
particulary copy/pasta and should be converted to a table-driven loop
reusing the same logic.

message header.

Updated some comments in smbdefs.h too.

If a message sub-board is configured to "Allow Message Tagging"
(under Toggle Options in SCFG->Message Areas), then after a message is
posted (via the terminal server), the user will be prompted if they
want to tag the message with one or more space-separated tags. The no/yes
prompt can be skipp if desired by setting the TagMessageQ line in the
text.dat file to an empty string. There is currently no provision for
regular users to actually see/view the message tags (yet), but the sysop
or sub-op can view the tags in the message header with the 'H' sys/sub-op
command.

smb_nettype() now return "FidoNet" instead of "Fidonet" for NET_FIDO
(for not particularly good reason).

Fixed some funny typos in comments.

QWKnet call-outs. Hopefully help debug Mortifis' problem with QWKnet
call-outs.

(stops parsing/displaying upon Ctrl-Z) - this solves the SAUCE record
issue for sysops (e.g. using PabloDraw).

always include the text description of the last error and the line number.
The logging of the smb.file string is probably redundant since that path
will likely be included in the last_error string.

messages (and maybe files in the future).

confusing with 3 bool settings (in the sbbsecho.ini) to represent 4 valid
security requirement levels, so I attempted to simply the menu options to
make it easy for sysops.
BinkpAllowPlainText now defaults to true since the supported encryption method
isn't even an official FidoNet standard, yet.
I also added/updated some online help (F1) help text.
Added an "Exiting" popup (like SCFG) when exiting.

Not sure why this file started with a "3.1" rev. Weird.

(telegram) sent to the pollster is now configurable via text.dat
(VoteNoticeFmt).

an error message (uifc dialog box) rather than just silently refuse to
display the upload file picker dialog. Bug reported by electrosys.

NULL. When history is NULL, treat TAB the same as before (in weird ways).
The TAB-completion algo is very simple: just find the first (case
insensitive) match in the history list and if there is one, use it as the
current string content.

posted vote msg - the format of the vote(s) is currently hard-coded and not
colorized/pretty. This'll require an update to the PollVoteNotice text.dat
line.

Also, the File() constructor will now properly complain if no filename
is passed.

of default style elements.

- ini_key_len
- ini_key_prefix
- ini_section_separator
- ini_value_separator
- ini_bit_separator
- ini_literal_separator

and no actual observed problem.

malloc'd strings.

elements (member variables) would be changed to point to a string constant.
Don't do that - instead just use local stack variables for those style
element default values. This leads the way to constifying the style arguments
in the future and allows the caller to use non-NULL style elements as indicator
of something that should be freed if the caller allocated some memory for it.

I have a new use for it in the v3 Terminal Server, it now follows the
"NO_DOS" option in the [bbs] section of the sbbs.ini file. So if you have
multiple Win32 instances of sbbs (like I do), but only some of them
support DOS programs, you can now use this ARS keyword to enable/disable
access to a program based on the existance of DOS support. For example,
I have some 16-bit DOS message editors where I had the ARS set to
"WIN32", but on my 64-bit Windows instance of sbbs (vert.synchro.net),
16-bit DOS programs aren't supported while on my 32-bit Windows instance
(bbs.synchro.net) they are. So I needed a good run-time check for whether
DOS programs were supported or not and this old ARS keyword seemed the
right fit. For Linux builds, this keyword will only evaluate to true if
built with the USE_DOSEMU option.
This is only true of the Terminal Server - use of "DOS" ARS keyword in
other servers and services will still just evaluate to "false".

"short name" (e.g. derived from the "AREA tag" from FILEGATE.ZXX) is the same
as a pre-existing dir, just over-write that dir - don't create a new one.

previous commit: don't clear the line counter or call pause() - which will
do nothing - if the console abort flag is set.

would not always auto-redisplay menu files when the user hits 'Q' (or 'N'
or Ctrl-C) at auto-pause prompts:

When displaying a "message" (e.g. file), if the console abort flag is set
before a single line has been displayed, clear the abort flag. This most
likely means a pause (hit a key) prompt was automatically displayed due to
a clear screen code in the message/file and the user hit 'Q' or 'N' or
Ctrl-C at the prompt. In this special case, don't treat that as an
"abort message" command and keep displaying the message/file.

Once one or more lines in the message/file have been displayed, then the
behavior is the same as before: a console abort (even as a result of an
auto-pause prompt key) will stop the display of the current message/file.

 term 0087 TLS ERROR 'Unexpected <Unknown type> (24) packet, expected application_data (23)' (-1) popping data
 message repeated 492 times: [ term 0087 TLS ERROR 'Unexpected <Unknown type> (24) packet, expected application_data (23)' (-1) popping data]

When using TLS with a JS Socket object, if there was any kind of data error,
the recvline() method would return a blank string rather than null/undefined.
nntpservice.js just loops when it receives a blank string, so this caused an
infinite loop (with disk-filling error log messages).

First change: if no data has been received (i == 0) and there's any kind of
receive error or timeout or disconnection, just return null. And not undefined,
but null (!) like in v3.15 (before the great JS engine update of 2000-mumble).
Also, there appeared to be a JS_RESUMEREQUEST call missing in the TLS error
return case - so that's another bug fixed.
Commented on the magic return values for js_sock_read_check()
and js_socket_recv().
Simplified js_sock_read_check() return value a tad: let the caller decide if
they want to do something special based on the value of 'i'.
Added some comments to make this code more readable.

We are now no longer treating the different error return values (0 and -1) from
js_socket_recv() special in this function, but we dont' treat them special in
any of the other calls in this file/object either, so that seems to be the
norm.

Deuce really wanted to pass 1000 as a value here (use 1 instead). I don't
know if this was an observable problem or not, but it certainly *looks*
like a bug.

first white-space character encountered.