Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

build 19 displaying ?[?25h?[4 q at the end of my prompt

M

mdlawler

Sep
191
3
Both in legacy console and compty modes I'm seeing ?[?25h?[4 q displayed at the end of my prompt which is obviously an ANSI sequence. I believe I'm running under Windows terminal in Windows 11, but I don't know how to tell programmatically. If I choose let Windows decide or run under Windows terminal I get the same behavior. I'm still getting conhost instead of openconsole so maybe I'm not really running under terminal.
 
This tells me that I am running TCC from Windows Terminal.
Code: 
E:\Utils>echo %_parent
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.24.10621.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe

This tells me that I am running TCC from a stand-alone TCC.
Code: 
R:\>echo %_parent
C:\WINDOWS\explorer.exe

Joe
 
Using the ProcTree plugin,
I get the following when run from a stand-alone TCC.
Code: 
R:\>proctree windowsterminal

542C  WindowsTerminal  109844 Shell 0 e:\utils
   ├──BC58  OpenConsole
   ├──FB08  OpenConsole
   ├──1596C  powershell
   └──1AD14  tcc  GDI+ Window (tcc.exe)
      └──12AC4  AutoHotkey64  C:\Program Files\AutoHotkey\UX\launcher.ahk - AutoHotkey v2.0.19
         └──59BC  AutoHotkey64  E:\Utils\tcc.ahk - AutoHotkey v2.0.19

Code: 
R:\>proctree

192E8  tcc  Admin: tcc36 - proctree
   ├──BBBC  conhost
   └──16484  eViewer  Take Command / TCC Help v. 36
      └──121FC  msedgewebview2
         ├──92B4  msedgewebview2
         ├──AC44  msedgewebview2
         ├──10CAC  msedgewebview2
         ├──19668  msedgewebview2
         ├──19E24  msedgewebview2
         └──1A7B0  msedgewebview2

Ref: ProcTree Plugin

Joe
 
Interesting! It doesn't show in my prompt but it seems to be doing exactly what it says ... turn the cursor on and make it a non-blinking underscore (which is not what I want).
 
mdlawler said:
Both in legacy console and compty modes I'm seeing ?[?25h?[4 q displayed at the end of my prompt which is obviously an ANSI sequence. I believe I'm running under Windows terminal in Windows 11, but I don't know how to tell programmatically. If I choose let Windows decide or run under Windows terminal I get the same behavior. I'm still getting conhost instead of openconsole so maybe I'm not really running under terminal.
Click to expand...

Those are ANSI sequences that WT is responsible for interpreting. It seems like you are not running in WT, but rather in a vanilla console with ANSI disabled.
 
rconn said:
Those are ANSI sequences that WT is responsible for interpreting. It seems like you are not running in WT, but rather in a vanilla console with ANSI disabled.
Click to expand...
Yes, checking ansi colors in options on the windows tab fixed the issue. I assume that WT is the future so I should run under that. How do I go about doing that with tcc running under tcmd?
 
mdlawler said:
Yes, checking ansi colors in options on the windows tab fixed the issue. I assume that WT is the future so I should run under that. How do I go about doing that with tcc running under tcmd?
Click to expand...

Either TCC running in TCMD or TCC running in Windows Terminal. TCMD and WT do not mix; they are doing the same thing (hosting ConPTY sessions in tab windows).
 
You must log in or register to reply here.
Back
Top