running SCFG on the repo.

This is a "forever bug". I guess at one time I stored each file's extended
description in a separate file? I don't know, but this remove() call is
clearly wrong.

If you have a local XML document containing an RSS or Atom feed,
you can point to it like: file:///this/is/where/it/is.xml.
For Dan_C, a variation on nelgin's proposed solution.

So we can display ¯\_(ツ)_/¯ in ASCII. It's really important.

¯\_(ツ)_/¯ <- also, UTF-8 test commit message test. :-)

Also optimization of spinning cursor: don't call strlen() for each spin

I stole one of these patterns from 'git-size'.

Inspired by the cool progress cursor displayed by 'git-size', the spinning
cursors in the Synchronet terminal server are now configurable via text.dat
strings (SpinningCursor0 - 9), no maximum length.
Increased the cursor "spin" rate from 4 to 5 times per second.
The first character of the spin pattern is chosen at random between 0 and 4
but the direction of increment is also from left to right.

- as requested (and insured) by Nelgin

Run-time dirs are ctrl, text, docs, exec, xtrn, web, node1

One can't have too many semicolons.

Rather than introduce yet-another-external-program/config flag to enable
the "new JS run-time/context" per invocation of any particular JS command,
I'm using the XTRN/EX_SH ("Use Shell") option as it had no function for
JavaScript command-lines and the concept is similar.

So if you want to invoke a JS external program/timed-event in its own
"sandbox", enable the "Use Shell / New Context" option for that
program/command in SCFG. There may be performance penalties when running
JS mods in this way, but you get the benefit of isolating one JS module
from all others, if/when necessary.

So revert the order back to the way it was in aa2bcd61
(don't you love these git references?).

Also, the previous fix for js_execfile() calls for global hot-key events also
fixed the EX_JS_CX feature I was working on (js_execmodule)!

Add another "get cryptlib error string" (at least, that's what I assume GCES
stands for) that allows the log level to be specified, rather than derived
from Cryptlib thinks the log level should be. Do this rather than adding one
(lowering the severity) of every cryptlib log message as I did in the previous
commit to this file.

As reported by Ragnarok and The Lizard Master, invoking a JS global
hot-key handler (e.g. hitting Ctrl-U or Ctrl-P with the privatemsg
or nodelist modules installed as handlers) would lead to the global
object being cleared/corrupted so other scripts would then fail to
run correctly (e.g. Error: can't open sbbsdefs.js: No such file or directory)

This probably explains the JS_GC/JS_ENDREQUEST change needed when
the hotkey-specific JS runtime/context/scope was introduced last year.
Should revisit that too.

Might as well use their bandwidth before my own.

(e.g. errors become warnings) - I'm tired of seeing this in my
error.log every day:
SEND/TLS ... ERROR 'Received TLS alert message: Handshake failure' (-15) setting session active

Also incremented the rev to 1.60.

Fix problem introduced in
b1ecd9b6 (August 8, 2019)

When sbbs_t::printfile() is used to display a file that is < 2MB in size
and the P_OPENCLOSE mode flag was not specified, the file is read and
displayed one line at a time. This allows for the quick display of very
large files. This was accomlished by calling sbbs_t::putmsg() for each
line. Unfortunately, putmsg() would save and restore console mode flags
like the auto-screen pause control flags stored in sbbs_t::sys_misc
so this would render some features like the POFF @-code, inoperable.
This problem was reported by WitNik with files displayed from
Bulleeye! Bulletins.

Other issues were discovered with the WORDWRAP/WRAPOFF @-codes.

Fixed with the addition of sbbs_t::putmsgfrag() which is used by
printfile() to display a message fragment (one line) without
saving/restoring console state flags.

Fix massive regression introduced in previous commit.

Iterate over RSS feed channels and items in a less ugly way.
Don't iterate over all item children and cherry-pick the ones
we want, just target the desired elements instead.

Remove the "This is shitty" comment. It's still shitty overall,
but that particular shitty thing has been de-shitted.

See merge request sbbs/sbbs!5

Iterate over RSS feed channels and items in a less ugly way.
Don't iterate over all item children and cherry-pick the ones
we want, just target the desired elements instead.

Remove the "This is shitty" comment. It's still shitty overall,
but that particular shitty thing has been de-shitted.