Support being the "far-end"

[davidrg]

These days, Windows has an SSH server. You can SSH into a windows machine and run the CLI version of Kermit 95 (k95.exe) just fine. But you can't use it as a "far-end" file transfer partner. Typing k95.exe -s oofa.txt at the windows shell doesn't work. And you can't launch k95, and give it a send oofa.txt either - both fail with an error because there is no active connection and K95 doesn't seem to support using stdin/stdout for file transfer.

This probably requires #59 to be resolved first, as K95 will be running inside a Windows PTY in these situations.

For being invoked from the command line (k95.exe -s oofa.txt), K95 will probably need to force on stdin/stdout mode (normally set via special command line parameters). For the interactive use case (send oofa.txt), K95 might have to do some extra work - perhaps temporarily switch to stdin/stdout if thats possible.

If this can all be made to work, then it might also be worthwhile looking into whats required to support 24bit color in CLI builds of K95 on modern Windows hosts using SGR control sequences to set attributes rather than NT console APIs.