This makes this file more suitable for import into SCFG->Message Areas
(something I'll work on soon), i.e. as an alternative to importing badareas.lst

55 characters (per echobase.hlp and .que in http://echolist.net/echohelp.zip).
... who knew?

when importing an echolist (e.g. badareas.lst) file, the storage path of the
template sub-board (if there was one) is cleared. Don't over-ride the template
sub's storage path unless a non-blank storage directory was specified in the
import file (e.g. subs.txt).

Possibly fix dupe dummy score on first run. Didn't test lol.

Added 'N' for immediate next wave.
ESC to quit still works, but now Q does too.

Tidied up a bit, but wow ... this is pretty bad. You'd think
I wrote most of it over the course of a drunken evening seven
years ago or something.

if there are no Fidonet addresses configured in SCFG->Networks->FidoNet.

Added CVS/rcs "Id" keyword, as all sbbs .js files should have.

Resolve a couple of CPU-sucking while(!console.inkey()); loops.

set the capabilities of sbbs (enable low-port binding)

This eliminates the error messages that would be displayed/logged when
attempting the SYS_capset SYSCALL, which fails when not root.

So the capabilities dance enabled with USE_LINUX_CAPS (which is automatically
enabled when /usr/include/sys/capabilites.h exists, which is installed with
the libcap2-dev package) apparently is still useful if you need to start
sbbs as root: the main thread will remain as root even when the child
threads have their user-id's changed to the user specified in the [UNIX]
section of sbbs.ini or on the command-line
- so reducing the enabled privilege set for this root/main thread to the
minimum needed, is a good security measure. It does this reduction (call to
linux_minprivs() after the call to change_user()) so I'm not exactly sure how
that works, but according to Deuce, this is what's happening. :-/

thing or how to test the change. <shrug>

time for it to go away. Using 'sudo setcap sbbs' during build seems like the
better, more supported solution.

the generated 'sbbs' executable to enable low-port-binding capability.
e.g. run 'make RELEASE=1 setcap symlinks' to make a release (non-debug)
build, set the bind-capability on sbbs, and create symlinks from your
exec directory to the build output (*.exe.release) directory.

progress, but [H]eader view and [C]hange attributes commands work, more or
less.

of external program names to be displayed:
32 chars in multicolumn mode
40 chars in singlecolumn mode

of external program names to be displayed:
32 chars in multicolumn mode
40 chars in singlecolumn mode

New modopts.ini [xtrn_sec] keys:
- multicolumn_separator (default: " ")
- singlecolumn_margin (default: 7)
- singlecolumn_height (default: screen rows - singlecolumn_margin)
- singlecolumn_lstfmt (default: "\x01h\x01c%3u \xb3 \x01n\x01c%s\x01h ")

Moved twitlist.cfg and spamblock.cfg to "Edit Filter File" menu.

nanosleep was interrupted by a signal and the SLEEP parameter is > 1.
Previously, any signal wuold abort SLEEP() prematurely. A SLEEP(1) (yield)
behaves the same as before since 1 is a special value where a short-sleep
duration is fine/expected on occasion.

Updated Menu Item names (e.g. "Configure BBS" rather "Run SCFG").
Added menu options to view echostats.ini and badareas.lst

(could create duplicate groups).
Added EchoList configuration to sbbsecho.ini (optional/prompted).

Fixed capitalization and description of "SBBSecho".

term.c:1033:23: warning: '%s' directive writing up to 4096 bytes into a region of size between 0 and 4096 [-Wformat-overflow=]
term.c:1033:5: note: 'sprintf' output between 2 and 8194 bytes into a destination of size 4097
term.c: In function 'xmodem_download':
term.c:1503:23: warning: 'sprintf' may write a terminating nul past the end of the destination [-Wformat-overflow=]
term.c:1503:5: note: 'sprintf' output 2 or more bytes (assuming 4098) into a destination of size 4097
term.c:1543:25: warning: 'sprintf' may write a terminating nul past the end of the destination [-Wformat-overflow=]
term.c:1543:7: note: 'sprintf' output 2 or more bytes (assuming 4098) into a destination of size 4097
term.c:1585:23: warning: 'sprintf' may write a terminating nul past the end of the destination [-Wformat-overflow=]
term.c:1585:5: note: 'sprintf' output 2 or more bytes (assuming 4098) into a destination of size 4097

Apparently removed some trailing whitespace characters too (thanks, Geany!).

bbslist.c:1336:44: warning: '%s' directive writing up to 1024 bytes into a region of size 536 [-Wformat-overflow=]
bbslist.c:1336:3: note: 'sprintf' output between 25 and 1049 bytes into a destination of size 560
bbslist.c:1342:44: warning: '%s' directive writing up to 1023 bytes into a region of size 376 [-Wformat-overflow=]
bbslist.c:1342:3: note: 'sprintf' output between 25 and 1048 bytes into a destination of size 400
bbslist.c:1343:44: warning: '%s' directive writing up to 1023 bytes into a region of size 296 [-Wformat-overflow=]
bbslist.c:1343:3: note: 'sprintf' output between 25 and 1048 bytes into a destination of size 320
bbslist.c:1344:44: warning: '%s' directive writing up to 4096 bytes into a region of size 216 [-Wformat-overflow=]
bbslist.c:1344:3: note: 'sprintf' output between 25 and 4121 bytes into a destination of size 240
bbslist.c:1345:45: warning: '%s' directive writing up to 1024 bytes into a region of size 136 [-Wformat-overflow=]
bbslist.c:1345:3: note: 'sprintf' output between 25 and 1049 bytes into a destination of size 160

the necesary functions for a re-implementation of asprintf().

any files), so use "del /q" instead.

Fixed some JSDOC strings.

Unexpected file path 's:\sbbs\fido\outbound\0067270f.hut' expected '../fido/outbound\0067270f.hut' (skipped)
Unexpected file path 's:\sbbs\fido\outbound\0067270f.hlo' expected '../fido/outbound\0067270f.hlo' (skipped)
Unexpected file path 's:\sbbs\fido\outbound.002\011801d0.clo' expected '../fido/outbound.002\011801d0.clo' (skipped)

Nah, seriously, though is anyone but me using PETSCII? :-)

"dump" to an array of strings using the (new) smb_msghdr_str_list() SMBLIB
function. The message header passed must've been previously returned from
the get_msg_header() or get_all_msg_headers() method.

A similar dump could be constructed from the header properties, as available in
JS, but that would be inconsistent with other msg header dumps and likely lack
header fields or details available from the lowest level dump method provided
in SMBLIB.

- ASCII
- UTF8
- CP437

And these, along with the pre-existing PETSCII keyword, are mutually exclusive
(only one will be set/true).

- you couldn't specify a maxnum value of 0 (it would get overridden to ~0)
- you couldn't specify a mode argument value without also specifying a non-zero
  maxnum value

(e.g. for the [O]perator->(H)eader dump command from the reading msgs prompt)
Looks pretty much the same as before.

list (str_list_t) where each string is a header field (variable or fixed) in
"<name> <value>" format. This format more closely resembles the output
of the sbbs_t::msghdr() function which is used to dump message headers
(e.g. for sysops/sub-ops).

I intend to replace the duplicate logic in sbbs_t::msghdr() with this new
function.

I would have liked to have used a list of named strings (named_string_t), but
I don't yet have a library to alloc/add items to a named string list.

is actually an authenticated local user (when usernum != 0).

msg_client_hfields() no longer saves the client->user as the SMB SENDERUSERID
hfield when the client hasn't been authenticated (as is the case with normal
SMTP). The SENDUSERIDs were redundant and misleading for unauthenticated
SMTP-received mail messages, so that's now fixed.

these are printf-style functions for inserting or appending a string into a
string list.

Newly posted replies (by the current user) did not appear in the message list.
The message list was never re-loaded: I added a Ctrl-R command key to reload
the message list manually and it's also automatically reloaded when replying
via a public-posted message (email replies don't force a reload).

The sub-board's last-read pointer is also updated whenever the current msg
selection is moved, even if the message isn't read or previewed. This paves
the way for the internal message reader to possibly track to the current
message selected in the msglist module upon exit.

Included in here is a work-around for the (just-fixed) MsgBase.get_index/
get_all_msg_headers() bug where the msgbase status header was not re-read
before determining the max number of messages to load. That work-around will
be removed eventually.