The other 500 times are implied.

The reason the comparison was changed to <= 0 is to do an explcit
check that eliminates negative numbers rather than the implicit ones
with the greater-than checks.

It seems that GCC is concerned that we can't create a sftp_dirdescriptor_t
or sftp_filedescriptor_t?

Add initial support for SFTP

See merge request !415

SlyEdit DCT: Fix so that the quote window bottom border is drawn the full width, not 2 characters short (not sure why this started happening)

See merge request !416

SlyEdit DCT: Fix so that the quote window bottom border is drawn the full width, not 2 characters short (not sure why this started happening)

If user is being kicked off for being on "More than one node at a time", then
don't send a message to other any other nodes that the user logged-on
successfully (they haven't). Previosuly, it'd send messages to all the
lower-numbered nodes that were in-use (but not by the same user).

Reported by Nelgin.

User disconnection will trigger auto-terminate (eventually) as well. But only
in the terminal server.

JS console.inkey() and friends use this as the underlying function to get
input from the TCP socket.

This might address issue #725

Hoping Nelgin will let us know.

For some reason, I committed test code that commented-out the actual call
to js_IsTerminated() which avoided the unnecessary error log message. I guess
I was testing to confirm the change actually worked. <shrug>

Address this problem report:
<nelgin> Right but I'm getting a lot of "logged off" without ever having a "logged on"
<nelgin> Node 3: Keyop logged off 02/26/24 18:35:45
<nelgin> Node 5: Keyop logged off 02/26/24 18:36:39
<nelgin> There was never a login, so there can't be a logoff.
<nelgin> That would break the time-warp continium.
<nelgin> time-space whatever :)

This could happen when non-G-exempt user was kicked before logon completed due
to already being logged onto another node. This change should fix that.

(just a cosmetic change)

... when run from the BBS (terminal server)

If errno is 0, it's definitely no proividing anything of value here. Of
course, sometimes errno might be non-zero and still be unrelated to the error
message. <shrug>

For Nelgin:
!ERROR 0 (Success) in exec.cpp line 644 (js_execfile) compiling "something.js" access=0
<nelgin> I don't quite get why a successful execution is logged as an error

Resolve build warning about unused var

Also, resove a new gcc warning about signed/unsigned compares.

Converts UTF-8 output to CP437 equivalent (cterm doesn't yet support UTF-8).
Fixes issue #717 (more or less).

The terminal dimensions are also read from the node*/terminal.ini file, but
aren't applied to the cterm runtime (though maybe they can/should be, probably
requires a cterm re-init).

... so no need to parse/strip them here.

This eliviates the issue of partial/corrupted UTF-8 sequences when spying on a
node serving a UTF-8 terminal.

SlyEdit DCT: Use Math.floor() to create an actual number instead of toFixed(0) like I was in some very old parts of the code.  This fixes some cursor position calculations (for the current time, particularly).

See merge request !414

Eric Oulashin authored 1 year ago and Rob Swindell committed 1 year ago

SlyEdit DCT: Use Math.floor() to create an actual number instead of toFixed(0) like I was in some very old parts of the code.  This fixes some cursor position calculations (for the current time, particularly).

_fintfirst() is declared in the Mingw-w64 headers as an intptr_t,
which tracks.  Can't find _findfirst on MSDN, so that's good enough
for me... let's see what the pipeline says.

mingw32 has been dead for years, and is missing huge swaths of the
Windows APIs.  strerror_s() was the straw that broke the camels
back here, but there's a lot of hackery for it.

I'm not going to go through and actually remove the build support
yet since I may want to do the 1.2 SyncTERM release with it (though
likely not), but it's not long for this world.

Added NEW-ENVIRON. Note the variable is NEW_ENVIRON

See merge request !413

The definition of vsnprintf as _vsnprintf didn't seem to hurt the build
(as well, for Borland)

The GNU_SOURCE build of this function was (sometimes?) just returning the
string and not actually copying it to the passed buf. This is consistent
with the GNU manpage on strerror_r():
"This may be either a pointer to a string that the function stores in buf ..."
but was inconsistent with all the other build types of this function.

Also updated to use strlcpy and write the problematic error number to the
default string (if unknown).

As Nelgin pointed out, a Socket.connect() failure for reasons of address/host
lookup failure would report a stale/nonsense Socket.error/error_str value.

This change required us to query/store the socket API/getaddrinfo error string
at the time of failure (for the Socket.error_str property value) rather than
converting from number to string at the time the property is read.

This does mean that sometimes Socket.error is a errno value and sometimes its
a getaddrinfo (EAI_*) error value. Since the EAI_* values are negative, it
should be obvious which is which.