SlyEdit version 1.32: Added the ability to choose a tagline to append to the message upon saving.  Also added user settings, which lets users configure whether or not they want to use taglines, whether or not to prepend the original author's intials to quoted lines, and whether or not to indent quoted lines that begin with author's initials.  Also made some misc. changes & bug fixes, such as:
- The maximum message name length in Ice mode is now 35 characters (up from 20 characters).
- The user's time left is now updated on the screen as it changes (checked & updated after each keypress).
- Bug fix: The time is now displayed in the correct location when the terminal is wider than 80 characters.
- Bug fix for DCT mode: Listing text replacements using Ctrl-T from the Help menu now works.
- Bug fix for DCT mode: Fixed an off-by-one bug for the horizontal position of the INS/OVR text when changing between insert & overwrite mode using a terminal size more than 80 characters wide.
- Some color setting name changes & addition in the color theme configuration files.

don't read/write the file for *every* property!
Fixed several apparent memory leaks (upon errors) and at least one
freed-pointer usage.

header fields, not just the filler portion) - much more sane.

deletion by the maintenance process).

Don't reset the origin zone in import_netmail().
Fix-up type 2+ packet header parsing (ugh this is ugly).

Use zone information from packet header (rather than default/system zone)
since packed message headers don't zone information - use this address
for replying to AREAFIX requests.

Joe Delahaye.
Increment version to 2.21.

or 'longs'. Amazing that no one noticed.

int is 64-bit (not 32-bit).

(needs non-buffered stream).
Change error messages to use a log level of warning.

MS's CRTL throws an assertion. Buffer size must be >=2.

than never?).

(e.g. "in private chat with digital man" rather than
"in private chat with sysop").

"local chat with sysop" rather than "private chat with node 0".

don't try to run it. Previously it would display an error to the user:
"Sorry, you have insufficient access to run that program" (which is confusing
for the user).

value in node status (e.g. for local chat user event).

<Deuce> It sohuldn't be passing strchr(str, 0) as a macro argument.
<Deuce> Pop that bugger into a temp char * and she'll be golden.
<Deuce> If you could make/commit that change for me, that'd be great

counter/limits as branch counter/limits.

It currently only supports local (sysop) chat (call it with the '-l' argument),
does not support split-screen chat (for the remote user), and needs a lot
more testing and optimization. But for now, it serves as an example of what
is needed to write a private/sysop-chat module in JS, compatible with the
SBBS-Win32 chat.exe, for example.

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.
Don't change the current node's action (to XTRN) if it's currently PCHT
(private chat) as that's a signal to the local sysop chat app that the user
has disconnected.

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.

options.

as spammers are now hijacking common/valid mail subjects (e.g.
"Google Email Verification") for their spam messages and blocking all msgs with
such subjects is too heavy-handed an approach. :-(