Subj : Re: Commandline Telnet Client...
To   : Shurato
From : fusion
Date : Wed Feb 07 2024 11:16 am

On 06 Feb 2024, Shurato said the following...
 
 Sh> understand why none of the windows CLI options (Microsoft telnet, cygwin
 Sh> telnet and plink.exe) work as well as the linux one.  I'm using a Debian

do these telnet clients render correctly in "windows terminal" ? (get it in the app store) without syncterm or anything between?

windows actually has an api call to turn ansi parsing on and off, since "classic" windows text mode programs shouldn't have built in ansi support (unless the programmer programmed it custom themselves, like mtelnet, or probably one of the syncterm output modes) and programs that know how to do it can just turn on the modern one.

it's also possible that depending on how you run it, telnet behaves differently. it might be trying to parse ansi. the linux telnet program should
be fairly transparent since it never had to parse ansi at all. (syncterm is doing it)

this post: https://stackoverflow.com/questions/51680709/colored-text-output-in-powershell-
console-using-ansi-vt100-codes

outlines a systemwide change to turn the Virtual Terminal stuff on by default.. though i'm not sure if it'll be much help. i remember writing a small program that turned it on and then spawned plink (think like: spawning a bbs door. it's running "inside" the little program so it shares the setting) the bottom post on there has the api call to do that if you're able to program something like that.

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
 * Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)

.