Isn't that odd? I'm not using TCMD. When I use no inifile, how's ANSI32.DLL getting into TCC? If I use an inifile with "ANSI=No", then I really get no ANSI.I have "ANSI=Yes" and it misbehaves (without ANSI32.DLL loaded). If I start TCC with no inifile (/ii) I still get colors, ANSI32.DLL is loaded, and it doesn't misbehave.
You're right. With no inifile, I get AutoRun and AutoRun does it. I could never understand "Yes" being the default for AutoRun. That file is very likely to have CMD-specific stuff in it (like DOSKEY macros). The help seems to suggest that "No" is the default.TCC will not load ansi32.dll, ever. You have something else in your system doing that.
AutoRun : If enabled ...
I'm not sure what you're saying. I have had "ANSI=Yes" in every version of 4NT/TCC since ANSI support began. "ECHO ^e" shows the left-pointing arrow in every version I have (back to v8) except v22.You do realize that you cannot print an escape when you're using ANSI output, don't you? Unless you send the ANSI sequence to print control characters, it will just get swallowed.
It only "worked" because prior versions of TCC didn't implement the full x3.64 set.I'm not sure what you're saying. I have had "ANSI=Yes" in every version of 4NT/TCC since ANSI support began. "ECHO ^e" shows the left-pointing arrow in every version I have (back to v8) except v22.
So "ECHO ^e^e" should mean show me the graphical representation of character 0x1B? That doesn't work either and also leaves a peculiar after-effect.The ANSI driver (correctly!) interprets this to mean "show the following control character as a graphical character". So what you're seeing is the <CR> being converted to its graphical representation.
Definitely not -- you're telling the ANSI driver that you always want an escape to be displayed as a graphical character, not interpreted as an escape sequence.
Everything above is WAD.
Yes, and I've had dozens of requests to support all the VT100 sequences when not using the Windows 10 console ANSI.Does all this have anything to do with Windows 10 having VT100 emulation? I'd like to hear from someone who appraciates these changes. Have you seen https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences
I don't know what you mean by "see again". You can set top & bottom margins with DECSTBM (ESC[#;#r), but that was never supported in TCC before v22.The only thing I'd like to see again is the ability to set the scrolling region, so, for example, the first or last line of a console can be used as a "banner". Is that possible with TCC and Windows 10?
They emulated VT100.That is/was a VT100 feature; it didn't have anything to do with Coherent / Unix / Linux.
But you can't have DECSTBM if you also want me to remove all the 2-character escape sequences; they're intertwined.
And it works! ... well, it sort of works. If, in my 52-line console, IThe DECSTBM feature is supported in TCMD or TCC v22 running any version of Windows.
|Thread starter||Similar threads||Forum||Replies||Date|
|ANSI Colors Windows 7 no longer working||Support||6|
|WAD ANSI issue||Support||3|
|R||Batch Debugger Command Expansion Window||Support||3|
|A||Fixed v25 regression: Parameter expansion fails in piped commands||Support||2|
|IDE: After undocking the command expansion Window is offended||Support||2|