they were already created/configured:
- fidoin
- fidoout
- binkout
- binkpoll

!JavaScript  /sbbs/xtrn/lord2/lord2.js line 2264: ReferenceError: draw_menu is
not defined

line 147: ReferenceError: KMSG is not defined
Thanks wkitty42!

(rather than leaving the default disabled BINKP service configuration
in tact)

ie: Does not return if the path was made or not.

to before the actual export, so that if an area has no downlinks, you won't
actually see this errorneous but harmless log message. Also include the
"export-to" address in the message.

mutexes are undefined in children.

it before redirecting stdout to the pipe.

Likely fixes CGI errors seen by alterego (and has been broken for almost
fifteen years).

Reported by DigitalMan

- update_msg_attr() was disabled (just returned true), apparenly from a
  previous debugging session
- the DEL key while listing msgs didn't call update_msg_attr()

There is still a bug whereby viewing a message does not display its current
/updated attributes. Still need to resolve that one.

list, e.g. from 'F'ind text).
Fix a couple of typos/copy-paste errors in options:
- preview_properties_maxlen
- attr_sent

to match the settings on the BBS-side (e.g. iCE colors enabled/disabled).

Reported by belthesar... thanks!

Avoid gratuitous xim reallocations (not a bug)
Avoid gratuitous redraws (not a bug)
Avoid posting and waiting on a semaphore from the same thread (ehhhh....)
After blocking on XNextEvent(), drain all X events in the queue (not a bug)

Also not an issue.

This didn't cause problems, but it was confusing.

passed.

Fixed but I think DigitalMan reported where the count of entries isn't
updated after and add/delete until you change to the settings menu and back.

If this option is set, it means that all content available via http:// is
available at the same https:// URL.  This will trigger to new behaviours:
1) If an HTTP request has the "Upgrade-Insecure-Requests: 1" header, the
   client will get a 307 redirect to the https:// URL.
2) For https:// responses, the following two headers will be added:
   Content-Security-Policy: block-all-mixed-content
   Strict-Transport-Security: max-age=10886400; preload

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fb3be8ce071 in do_cgi_stuff (session=0x7fb2fbfaac40, cgi=0x7fb2fbfaa850, orig_keep=1) at websrvr.c:4376
4376                                                            SKIP_WHITESPACE(value);

is Custom, and you modify the custom mode.

This uses global pointers to automatic variables... and other insane things.

For cross-posting, to make sure the user can post in a sub-board, SlyEdit now checks the can_post property of the sub-board rather than checking the ARS.  The can_post property covers more cases (such as whether the sub-board is a networked sub and the user has the N restriction).

Incremented the version to 1.72 and date to 2020-03-04 to be up to date with today's release of SlyEdit.

Added support for a new option in SlyEdit.cfg: allowSpellCheck, which specifies whether or not the spell check feature is allowed. Valid values are true and false; it defaults to true if not specified.  You might want to disable spell check if, for instance, the spell check feature causes an "out of memory" error on your system.

New configuration option: allowSpellCheck.  This specifies whether the spell check feature is allowed or not.  It defaults to true if not specified.  You might want to disable spell check if, for instance, the spell check feature causes an "out of memory" error on your system.

Re-indented some functions to be more consistent with other code in SlyEdit.  No change in behavior.

The postMsgToSubBoard() function now checks to ensure the user has posting access to the sub-board before posting the message.  For cross-posting, SlyEdit already does not allow the user to select sub-boards they can't post in, but I figured it wouldn't hurt to have this function check for that before posting the message.