Why some software which outputs colours in ANSI code cannot display colours normally under Take Command?

[DOSforever]

Take Windows 7 , Take Command 25 environment as an example, check ANSI=1 by setdos command to make sure ANSI is enabled.

Eli Fulkerson's tcping.exe program supports the following two colour output methods
--ansi : Use ANSI colour sequences (cygwin)
--color: Use Windows colour sequences
After testing, the --color option can output colours under Take Command.
The --ansi option gives you ANSI colour sequences.

Also, if you use the yt-dlp.exe --color always option to force colours to be output, you get the same result.

So what is the difference between the ANSI colour output supported by Take Command and the ANSI colour output of these programs? How can Take Command also support colour output from these programs?

Translated with DeepL.com (free version)

 

[vefatica]

In TCMD, OptionsMenu\TakeCommand\Tabs, do you have an "ANSI colors" check box? If so, and it's not checked, check it.

 

[Charles Dye]

In TCMD, OptionsMenu\TakeCommand\Tabs, do you have an "ANSI colors" check box? If so, and it's not checked, check it.

Do you need to restart Take Command after changing this setting? (No, I honestly don't know.)

 

[vefatica]

Do you need to restart Take Command after changing this setting? (No, I honestly don't know.)

I don't know either. I don't even see the setting, probably because I have Windows 10. But it's mentioned in v25's help.

 

[DOSforever]

In TCMD, OptionsMenu\TakeCommand\Tabs, do you have an "ANSI colors" check box? If so, and it's not checked, check it.

In TCMD, OptionsMenu\TakeCommand\Tabs, I can not see any "ANSI colors" check box.

There is an "ANSI colors" checkbox only in OptionsMenu\TCC\Windows\Colors.

This checkbox has been ticked since the first time I used Take Command.

 

[vefatica]

I was just guessing. The TakeCommand\Options\Tabs tab's help says this.

Take Command Tabs Configuration Dialog

ANSI colors enables ANSI escape sequence support for all console applications running in Take Command tab windows. If you are running Windows 10 Creators Update (or later), Take Command will use the built-in console ANSI support. If you are running an earlier version of Windows, Take Command will inject a dll (ANSI32.dll or ANSI64.dll) into the console applications it starts. Note that if you have enabled ANSI colors in Take Command, you should disable ANSI support in TCC (OPTION / Windows).

 

[vefatica]

That might be saying (I'm guessing again) that, in TCMD.INI, you should have ANSI=Yes in the [TakeCommand] section and ANSI=No in the [4NT] section.

 

[DOSforever]

That might be saying (I'm guessing again) that, in TCMD.INI, you should have ANSI=Yes in the [TakeCommand] section and ANSI=No in the [4NT] section.

I tried what you said, and it doesn't work no matter how I change the values in these two places. I don't know if it's related to the Windows and Take Command versions.

 

[Charles Dye]

Oh, I think I know. In Windows 10, ANSI is handled by the console — and only the new console does this. You have to turn off the legacy console and restart:

 

[vefatica]

He said he has Windows 7.

 

[Charles Dye]

He said he has Windows 7.

Ah, I missed that.

 

[Jay Sage]

And what was that about "TCC v34" Properties?

 

[Charles Dye]

And what was that about "TCC v34" Properties?

That's the console properties dialog — exactly the same as the console props dialog for v33, or TCC/LE, or CMD, or any other console program.

Spoiler

Yeah, that's a beta build.

 

[Jay Sage]

What a surprise: There's actually a version 34 in the works

 

[vefatica]

What a surprise: There's actually a version 34 in the works

I think there's always a next_version in the works. Beta testers get their hands on it a while before it's released. So stay tuned.

 

[Jay Sage]

I'm tuned. I'm attuned. I haven't even finished installing version 33 on all my computers, but I still can't wait to get version 34 (let alone version 35).

I used to hold off on getting new versions because of all the work to get the settings reconfigured, but I've now managed to streamline them. My TCSTART and TCEXIT files and aliases adapt to the version, and I have documented most of the manual customizations required in the TCC and TCMD options and the "More commands..." options. If I could figure out how to write out all the settings to an XML file and then read them into a new version, all would be nearly trivial.