SlyEdit version 1.43 - Minor bug fixes: Sometimes SlyEdit would insert an extra empty line in the quote lines when replying to a message after wrapping long quote lines.  Also, sometimes SlyEdit would add an extra space to the beginning of some quote lines after wrapping them.

in the dir pane.

traversed.  The existance of the pnode variable implies this was the intent

in help output.

that was crashing the last time I tried to use this feature.

SMB message header fields (msg_auxattr and msg_netattr), as requested by
AccessDenied, though most of these attribute flags are currently never set by
anything. <shrug>

This results in *.vcxproj files not being detected as ascii since they have a
UTF-8 BOM at the beginning (and are therefore not ASCII).

Use perl to strip CRs from crypt32.vcxproj to allow the patch to apply cleanly.

scripts.

If the socket is not close()ed, it results in a socket descriptor leak, and on
*nix systems, FD_SET() may corrupt memory outside of the fd_set if a socket
descriptor higher than FD_SETSIZE is set.

This manifested itself via ircd.js which called connect() to servers, but never
called close().  After many hours, the next socket descriptor was higher than
1024 (default FD_SETSIZE), and resulted in corruption of the private data pointer
in js_socket.c:js_connect()... which in turn resulted in a crash.

defines XPDEV_THREAD_SAFE (not currently used in Windows builds) and
LINK_LIST_THREADSAFE (notice the inconsistent use of underscore :-)

defines XPDEV_THREAD_SAFE (not currently used in Windows builds) and
LINK_LIST_THREADSAFE (notice the inconsistent use of underscore :-)
Use of this property sheet fixes the problem with the terminal server global
variable 'uptime' getting corrupted when jsrt_GetNew() called listInit() from
js_rtpool.c which didn't #include sbbs.h and therefore had a different idea
about the size of link_list_t and thus corrupted the global data region
(zeroing out the 'uptime' variable, probably amonst other important things).

defines XPDEV_THREAD_SAFE (not currently used in Windows builds) and
LINK_LIST_THREADSAFE (notice the inconsistent use of underscore :-)

if time_t is unsigned and the current time is less than uptime.

There's comments that suggest the time(NULL) value is influenced by the
timezone, so possibly therre's a usage of it somewhere with the timezone
not being set comparing to an uptime that was set when timezone *was* set.
In this case, @UPTIME@ will say it's been up for zero days until the timezone
is set in that thread/process, or time(NULL) passes uptime.

the data/error.log.

is truly interested for historic reasons or whatever.

is truly interested for historic reasons or whatever.

require it).
Committed on the Free edition of March Hare Software CVSNT Client.
Upgrade to CVS Suite for more features and support:
http://march-hare.com/cvsnt/

Committed on the Free edition of March Hare Software CVSNT Client.
Upgrade to CVS Suite for more features and support:
http://march-hare.com/cvsnt/

FTP server.

Bug-fix: daily statistics and free-credits-per-day were not reset when the user
logged in via HTTP. This affected: posts_today, emails_today, free_credits,
timeon_today, and extra time values (e.g. posts_today would contnue to
accumulate potentially affecting uh... hand-wavey stuff). getuserdat() does the
necessary value resets, we just needed to write the entire user record back to
disk upon successfull login, rather than just updating specific fields in the
user record on disk.

logged in via FTP. This affected: posts_today, emails_today, free_credits,
timeon_today, and extra time values (e.g. posts_today would contnue to
accumulate potentially affecting the users ability to post via FTP-uploaded REP
packet). getuserdat() does the necessary value resets, we just needed to write
the entire user record back to disk upon successfull login, rather than just
updating specific fields in the user record on disk. The HTTP server looks like
it might have the same/similar bug.

Broken in rev 1.561 by Deuce:
"Remove *_TO_STRING() and remove some uselss code to return a string value from
the log() JS command." - the "useless code" enabled behavior which the
listserver.js (and possible other JS scripts) depend on.

disabled in the listserver.ini file.

commands (and avoid MIME issues).

Beautify and fix the "help" command response (include command descriptions).
Added support for Majordomo-like "who" command for SMTP-authenticated sysops
(only).
Subscribe, unsubscribe, and who commands support '*' as the list name to act
on ALL lists.