Remember the currently selected option on variable-length menus that might
scroll (using the "bar" var/pointer thing for uifc.list).

support in putmsg/printfile, etc. on per-use basis.
Add per-sub-board P-mode flags (so "Extra Attribute Codes" can be disabled
on a per-sub-board basis).

(e.g. [ and ]).

The global one is executed after all files have been processed.
A per-file command is executed after that file has been copied (if it
was copied successfully).
Command line specifiers are supported in both cases. In the global
command, %f is the TIC file path, and %s is the extraction dir.  In
a per-file command, %f is the destination file, and %s is the source.
This will remain untested until I receive some files to process.

Ctrl-A codes over QWK - excluding Ctrl-A P (pause), L (CLS), and comma (delay)
which were also previously allowed. These other codes can be problematic for
viewers and aren't well-suited to non-scrolling/full-screen message viewing
environments.

the Ctrl-A codes: L (CLS), < (backspace), [ (CR), or ] (LF).

Correctly support CR-terminated FTN-kludge lines (per spec, no LF is required).
Save the revision of this source file as the editor details for raw (writemsg)
and internal (msgeditor) created messages.

@-codes are also supported (i.e. displaying sysop-controlled content).

When message text contains an invalid or possibly dangerous Ctrl-A code,
convert the Ctrl-A to an '@' char.
Only Ctrl-A *attribute* codes will be allowed in message text
(e.g. not ^AP, ^AL, ^A", etc.).

start of a valid control paragraph (kludge line), then convert the Ctrl-A char
to an '@'. This handles the situation where someone quotes control paragraphs
with Ctrl-A chars, for example, we don't want those Ctrl-A chars being
misinterpreted as Ctrl-A codes causing weird colors or pauses or whatever.

Basically nodelist_handler.js, but less specialized.
Usage example in comments; should wikify that.
These are all "file handlers", but I canvassed a total of
three Synchronet sysops and they all shrugged and said
something like:
<DigitalMan> file_handler seems fine

"blink fonts" have been loaded into the terminal.

user, it is better to use bbs.compare_ars() rather than user.compare_ars():
- The "SYSOP" keyword automatically takes the "temp sysop" state into account
- The terminal capabilities keywords (e.g. ANSI, RIP, etc.) work correctly for
  auto-detected terminal capabilities (which are *not* stored in the userbase)

@-code in the yesno/noyesbar modules. Questions can span multiple lines, so
the string length is not a good indicator that it would wrap the terminal
screen, unintentionally.

vidparam structure itself.

HEADERS.DAT.

FIDOCHARSET, no longer FIDOCTRL.

FIDOCHARSET
Export CHRS: control line with value determined by sub-board settings (e.g.
ASCII only) and the contents of the message (UTF-8 or CP437).
Import "NOTE:" control line values into the SMB_EDITOR hfield and export
from SMB_EDITOR -> NOTE:.
Increment SBBSecho version to 3.08.

And remove the "CHRS: " portion of the FIDO_CHARSET_UTF8 definition as we're
now storing these values in their own SMB hfields (FIDOCHARSET), not FIDOCTRL.

FIDOCHARSET
with its own smbmsg_t convenience pointer: ftn_charset.
this allows greater control over when/how this header field is exported.
Constify smb_msg_is_utf8().
Note that the "Editor" hfield type should hold any FTN "NOTE" control line
values (where msg editor details/version are normally propagated over FidoNet).

Replacement for Baja TEXT_FILE_SECTION and JS bbs.text_sec() functions.
Ported from src/sbbs3/text_sec.cpp

You run it from a Baja module with: exec_bin text_sec

This is a work-alike port of one of the oldest/cruftiest bits of C code in
Synchronet with no improvements in look or usability.
1. I want to eventually start deleting all the redundant C/C++ code in sbbs,
   so that's one reason why I've been creating these *_sec.js modules, and
2. I think this "section" of the BBS could use some significant improvement
   and didn't want to do any of that in C/C++ - this is clearly a JavaScript
   task. But I wanted to start with the identical functionality and improve
   from there.

(e.g. for UTF-8 Fido or QWK netmail messages sent over SMTP or POP3).

instead of "charset=IBM437", when appropriate.

instead of "charset=IBM437", when appropriate.

FAQ.

When set to true, enables group read permissions on the ssl.cert file
(using the new file_chmod() global function).