That would definitely be a nightmare to modify the TCC code. At a minimum, thousands of lines of code. And a guarantee of breaking existing aliases and batch files.

You cannot specify multiple /Ix options. If you want to turn multiple options off, use the /Ixxx format. I will make this clearer in the help.

Pipes are not handled by the system, they are handled by the command processor (TCC or CMD or PowerShell etc.). If you are piping to an external command, TCC executes that command directly, not through another shell. If you are piping to an internal command, batch file, or alias, TCC has to...

That's up to the Scintilla Powershell lexer, which I didn't write.

That's an odd message (and not reproducible here), because (1) TCEdit isn't a dynamic link library, and (2) that code hasn't changed for quite a while, and (3) Sci_IsSelection is called in IDE.EXE and in TCMD.EXE as well. Do you get errors there or only with TCEdit?

It's a command variable, not an internal variable. Command variables are only documented in their respective commands.

I don't doubt that something is affecting your privileges - but it isn't TCC. There is no code in the TIME function that sets privileges. Are you running this in an elevated session?

It seems as if you've got a "white on white" text colors setting somewhere. (The old hidden console windows checked for that and switched to a visible display; the ConPTY windows assume you meant to do that.) Are you starting a TCC tab window (the default)? Try starting TCC from a CMD command...

TCC does not try to access the internet at startup to check the registration. However, TCC does try to validate the authenticode signature on TCC.EXE and TAKECMD.DLL, by calling WinVerifyTrust., which in turn calls Windows' certificate-chain engine. If there is a missing local intermediate/root...

Which means TCC is either running in a TCMD tab or a Windows Terminal tab.

Are you running TCC in a TCMD tab window, a Windows Terminal tab, or as a bare conhost session? Try starting TCC with the debug option (TCC /...). That will pop up message boxes showing the TCC initialization stages, and should help isolate where the delay is coming from. (If you don't see any...

So is 4DOS, but I'm not supporting either of them ...

The message is coming from Windows, not from TCC. Since TCC hasn't supported 32-bit for 10 years, I doubt this is worth trying to hack a new message into Windows.

You have ConPTY enabled, but do you have ANSI enabled? Those are ANSI escape sequences that are being displayed literally instead of interpreted as color resets.

I have uploaded 36.52.88 to the web site. Two fixes here: 1. Some fonts have bad ligature values that caused TCMD to calculate the wrong caret position and right margin. TCMD now validates the ligature values before using them. 2. OpenAI broke their APIs (again) with the 5.6 release. Four API...