GitLab

When a sysop wants to chat, he wants to chat right now, damnit!

Try that, Nelgin.

SCFG for Win32 is linked against a load_cfg lib that builds withOUT SCFG defined, so these compiled AR elements were allocated and then many SCFG operations (e.g. copy/paste, create new) would copy the allocated ARs to another configuration and then be subjected to double-free upon exit/clean-up (resulting in exception or crash).
Just get rid of this cruft and some other related RAM-byte-saving hold-overs from the MS-DOS days.

- nodelist (default: "nodelist")
- who's online (default: "nodelist -active")
- private message (default: "privatemsg")

This allows the nodelist and private message modules to be "installed" without
over-riding global hot key events (SCFG->External Programs->Global Hot Key
Events), allows the Baja functions NODELIST_ALL, NODELIST_USERS, and
PRIVATE_MESSAGE and JS bbs.list_nodes(), bbs.whos_online(), and
bbs.private_message() methods to use external modules (JS or Baja)
automatically.

The old C++ logic remains for these features if the module's are cleared (set
to a blank string) in SCFG, but at some point, that code will likely be removed.

when "extra raw" output is needed.
Use putcom() and comprintf() instead of rputs() and rprintf() for ANSI escape
sequences. This doesn't actually fix any problem, but since rputs() is
"less raw" than it used to be, let's use direct-output routines instead, for
ANSI output.

menu() if it does (exist) and doing something else if it doesn't.

and then hit 'Q', it would kick you out of multi-node chat (because
the abort flag was set).

sbbs::lputs() will log the current user alias already, logline()->lputs() would
create log messages with the user alias twice.

flags set manually in SCFG.

so they can be more easily used by external utils (e.g. umonitor).

buffer overrun concerns.

- if the sysop had text/menu/<filename>.bak (for example), the optoinal menu
  would attempt to load, resulting in an error ("<filename>.asc not found")
- if the sysop specified menu_file or menu_dir (e.g. via Baja), the existing
  checks for optional menu file existance would not work

chat, rather than the old startup options flag ([BBS]->SYSOP_AVAILABLE).
This will be much easier for other processes/programs to query and control.

paged by a user on the terminal server.

If an external progarm is configured (in SCFG->External Progarms) is configured
to "execute on event" set to "Local/Sysop Chat", then that program will be
executed when the remote user is "pulled" into sysop-chat (e.g. via F10 key in
sbbsctrl) rather than running the normal built-in chat.

That is, if any of the following text.dat entries are set to a blank/emtpy
string (by editing ctrl/text.dat or via run-time script modification), the
question will not be asked of the user allowing greater sysop-customization
of hard-coded processes (e.g. new user application):
ClearUploadQueueQ
ClearDownloadQueueQ
HangUpAfterXferQ
ChatWithGuruInsteadQ
ForwardMailQ
DownloadBatchQ
LogOffQ
DeleteErrorLogQ
ClearErrCounter
DeleteGuruLogQ
AutoTerminalQ
AnsiTerminalQ
ColorTerminalQ
ExAsciiTerminalQ
CallingFromNorthAmericaQ
ReadYourMailNowQ
NScanAllGrpsQ
SScanAllGrpsQ
NewPasswordQ
ContinueQ
EnterYourPhoneNumber
UserInfoCorrectQ
UseExternalEditorQ
DownloadAttachedFileQ
AddSubToNewScanQ (new)
RemoveFromNewScanQ
DisplaySubjectsOnlyQ
Post
SearchExtendedQ
ViewSysInfoFileQ
ViewLogonMsgQ
WithLineNumbersQ

Updated copyright dates.

make system.matchuserdata return an array of all matches if match_all==true, starting at usernumber if specified. (userdatdupe now takes an additional paremeter)

EX_STDOUT, defining EX_STDIO (to be both STDIN and STDOUT), adding XTRN_CONIO
and EX_CONIO (for future cioxtrn/doorway mode on Windows), change IO_INTS to
XTRN_STDIO

inserting (long) typedefs to prevent warnings, but in the case of the JS File()
class, actually supporting file lengths > 32-bit.

Added HOST and IP keywords to allow restricted access/privileges to/for
specific remote hostnames or IP addresses (wildcards allowed).
All string-argument type ARS keywords (e.g. SHELL, PROT, etc.) now support .can
style wildcards.
The current remote client is now used for protocol, host, and IP ARS checking,
when available, so this requires passing the client pointer around (which
explains why so many files are touched by this change) and takes care of a
long standing to-do item (the user's 'modem' value was used for the PROT
value checking, which was not always correct).

with ansi_gotoxy(), ansi_save(), and ansi_restore() functions.

enables read & write permissions for user & group & others.