I have already head about this (probably in this forum) but did never care. In french the label of the check box is translated as = en:"Use the inherited console (requires restarting, affect all consoles)", which is misleading ("inherited" and "legacy" have completely different meanings in the...

You are right, HKC\Console has keys for the program—I had never noticed or did not remember. I have also keys for the console window's title. I have 2 entries with …_powershell.exe, which had FaceName="Lucida Console" (not Raster); I changed these to "Consolas", but things don't work better. I...

Yes, I have already tried such manipulations. What I can do and it works: detach TCC, change the font of the TCC console, reattach the TCC console, and everything displays fine—but I have to do all this each time I open such a console, the change does not persist for the next console I open...

Yes, that's what the documentation says, but it is not clear if this means that FONT is actually designed not to have an effect from Take Command, or if this simply means that the effect of changing the font in TCC would not be visible in Take Command. In my case, the issue is not about how the...

I have set CHCP 65001 (for UTF-8). I have a .bat script (burried somewhere in the Microsoft Visual Studio\2019 directories) that changes TCC's font to a raster font, after which I can't see UTF-8 output in Take Command. I expected to change the font back with FONT /N"Consolas", but I can't get...

I have seen such issues using the same tcstart.btm on different computers; features accessing disks (%@ready, ISDIR) can stall (with a timeout) if the disk is not accessible on the computer. The same could occur with a VM.

I believe %-prefix to the function name is missing.

I gave it a try a few days ago. WINDOW DETACH did nothing: the tab remained in TCMD (I tried several times). Trying again today: the tab detaches, and the resulting console window works properly (as it should, and as I had always seen until recently). Looks like there is some problem sometimes...

I have used it in one or two cases, in order to play a long and repetitive sequence of clicks in a software (which I was debugging and I had to reach a given situation in order to debug). - It was just a single macro record; I did not play with multiple macro records (RECORDER/R); - AFAIU clicks...

I tried setting the full path SET COMSPEC=C:\Windows\system32\CMD.EXE. The behavior is the same: from time to time, TCC resets COMSPEC=<path>TCC.EXE.

I was lazy and wrote SET COMSPEC=CMD.EXE. Maybe TCC doesn't like the incomplete filename, and resets it to <path>\TCC.EXE.

The context: I run a software that lauches Perl>CMD>make>CMD>CL at a very fast pace. If COMSPEC=<path>\TCC.EXE, TCC gets launched instead of CMD, but this regularly hangs (I would say launching many TCC processes at the same time triggers some problems with some ressources). What I do: set...

It works without the quotes: echo %@regex[^-,-a] The documentation says the quotes are needed when there is a space in the expression. Maybe there is something confusing here because the caret is also an escape character for TCC.

I configure the keyboard with Sticky Keys: if you press and release Shift, then press 1, you get the exclamation mark. This does not work with Take Command; with Take Command the Shift must be pressed at the time you press 1. There has been a thread of discussion around this years ago.

You can write for %f in (file*.mkv) do (mkvpropedit.exe "%f" --edit info --set "title=Video Number %@name[%f]" This avoids the issue about ordering and counting.