COMSPEC is a command interpreter that other programs will use to execute commands. I have a few wrappers written in TCC, which had to redefine ComSpec back to CMD to make wrapped programs behave.

The INI file is the same for all variants: %AppData%\Local\JPSoft\TCMD.INI I have these settings for running .BTM files: $ ASSOC .btm .btm=takecommand.script $ FTYPE takecommand.script takecommand.script="C:\Programs\TCC-RT\tcc.exe" /B /C "%1" %* $ set PATHEXT...

IIRC, .btm is run in a separate process, unless explicitly CALL'ed.

Can you please try the mintty and compare your observations ?

That's why all my libs are open source. I don't like the thought of my work dying with me.

An off-topic, but if I were you, I'd move the ">" after the shell depth indicator. Or at least add a space ($S) to the end of the prompt.

Charles, There's a clear benefit to using merged holydays lists. Take for example religious holidays and country official holidays.

If you are using Windows 11, you can use the newly released M$ sudo tool.

I suggest posting this issue to windowblinds support. A simple desktop theming engine should not interact with such a basic system functionality.

Documentation clearly states that %* is a CMD compatibility and will always expand to all batch parameters.

Depending on how exactly you start explorer, it may open a window within your currently running desktop session without actually starting a new process. And to the sudo, I just use a relauncher. C:\Users\anrdaemon\bin\sudo.btm : @START "" /ELEVATED %*

Are you trying to re-implment the *nix script command?

What happened to bc ?

It's foolish to trust the AI blindly. It only knows what was published on the internet, and unable to critically evaluate it. Always read the documentation.

I frankly don't understand the masochism of those sticking to bare command prompt, when there are console file managers with much better experience.