How can this happen?? No commands work

[Claire_CJS]

Forgive me if I’ve posted something similar and don’t remember, but I’m just wondering how it is that the entire CLI can be broken such that no commands work......

  Unknown command: “endiff”  in: C:\BAT\check-for-missing-lyrics.bat 
      Line number:  316
⏸️ Pausing to allow time for this error to be discovered, but not stopping... [9997]^C

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>glh

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>d

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>d

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>dir

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>setdos /x0

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>d

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>exit

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>d

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>exit

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*exit

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>help

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>echo hi

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*echo hi

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>unalias *

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*echo hi

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*setdos /x0

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*echo hi

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>prompt $P$G

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*prompt

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*prompt $G

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*set prompt=!

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>prompt !

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*unalias *

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>*setdos

 <:㏘> <٪>  T:\new\MUSIC\Ween\MISC>ver

I had to give up and close it.

 

[rconn]

I've seen this happen (both in TCC and CMD) when the Windows ANSI processing has completely bollixed the console I/O. Usually because of some malformed ANSI escape sequences, or interrupting Windows in the middle of a sequence, or because the STDOUT handle is pointing somewhere other than the console.

Remember that TCC does not do any of the console I/O itself; that's all handled by Windows.

 

[Claire_CJS]

I've seen this happen (both in TCC and CMD) when the Windows ANSI processing has completely bollixed the console I/O. Usually because of some malformed ANSI escape sequences, or interrupting Windows in the middle of a sequence, or because the STDOUT handle is pointing somewhere other than the console.

Remember that TCC does not do any of the console I/O itself; that's all handled by Windows.

100% that must be what’s happening here.

I wish there was a way to turn this into a reportable/actionable bug for the Windows Terminal people... They’ve been doing a lot this past year and I want to strike while the iron is hot.

But yes. I am aborting scripts that send ANSI sequences. If only there was some atomic way to send each sequence.