Done DECSCUSR with parameter 0 for the Windows Terminal profile-specific cursor

[vefatica]

In other words, ^e[0 q. In WT, that will give the user-specified cursor. Please give users a way to specify it for insert or overstrike (or even both).

 

[rconn]

You realize that this cannot work in your preferred environment (WT + TCC)?

 

[vefatica]

Why not?

 

[rconn]

Because that code has to be in the ConPTY host app - i.e., either WT (I'm not rewriting WT) or TCMD (which you're not using).

 

[vefatica]

I still don't understand. I can manually emit any of ^e[n q for n=0 to 6 and WT does the right thing. Notably, when n=0 WT gives me the cursor configured in my TCC36 profile which is not one you can get with n=1 to 6. All I wanted was a way to get TCC to use ^e[0 q. WT knows what to do with it.

 

[rconn]

WT has no idea what to do with the insert mode cursor versus the overstrike cursor, which was the second part of your request.

 

[rconn]

As I explained in a previous thread on this topic, setting your cursor sizes to -1 means TCC will not send any ANSI cursor shape sequences, so you can send your ^e[n q sequence and get your default WT cursor. Which will be the same shape for insert & overstrike modes.

 

[vefatica]

I only set cursor sizes to -1 so TCC doesn't set a cursor I don't want. So I have to do it all myself. That's OK. I can get the switch between my WT configured cursor (for insert mode) and an alternative one for overstrike mode with a pretty simple keyhandler in my 4WT plugin.