36.52.87 command prompt and output scrambled

[Steven M. Geisler]

I just installed the 36.52 version over the original 36, and now the command prompt is scrambled, and the output of commands is chopped .
Below, the top is 36.52, and the one below is 32. I typed "C:\" and then "dir".

The original 36 that I was using was working as it should. I don't have the original 36 to reinstall.

 

[MGibs]

Do you have ANSI enabled in TCC Options

 

[Steven M. Geisler]

Do you have ANSI enabled in TCC Options

No. Neither does 32.

View attachment 6216

 

[rconn]

Those are ANSI sequences, specifically shell integration marks.

If you don't want shell integration, turn it off in the Take Command configuration dialog.

But I strongly recommend you turn on ANSI support, because it's used everywhere in ConPTY sessions.

 

[Steven M. Geisler]

Do you have ANSI enabled in TCC Options

View attachment 6216

I checked it, and it looks like that fixed it.

 

[Steven M. Geisler]

I'm still having problems. The ANSI stuff is gone, but the cursor starts before the prompt's end, and lines are being truncated. The 32 version's output is in the 2nd attachment.

 

[rconn]

Not reproducible here.

Please create an asciicast recording and send it (and your TCMD.INI and TCSTART, if any) to [email protected]

 

[Steven M. Geisler]

I looked up asciicast. It says it will record "ConPTY terminal sessions". Sorry, but I don't know what they are.
Keep in mind, I was using TakeCommand 36, the original when it was first available, with no problems. This started when I installed the 36.52.87 version the other day. That wiped out my original version 36 of TakeCommand and that version of the TCMD.INI, since the date modified is today. I'm attaching the one that's there now.

 

[Alpengreis]

@Steven M. Geisler

Just an idea ...

Do you set/call a THEME or so (within start.btm)? That could be the reason, because now, themes are supported natively which wasn't the case with beginning of v36 ...

 

[Steven M. Geisler]

No. The only theme I have is in "Options/Styles", Office 2016 black. I have no start.btm or any others except the JPSoft ones.
So when I looked at the themes, I saw Fonts also. In 32, I had Fonts selected as Extra Large.
I don't know what was in 36 (because it's gone), but I don't believe I changed it. I think I just used the same one I had in 32. But I notice now, in 36.52, there are 5 choices. System default is the first. I clicked that and restarted. Then it seems to be working. However, the font was way too small for me. So, I changed "Tab Windows" to Lucinda Console regular 12, which I've always used in Kedit, and it truncated again. So, I changed it to 10, and it went back to being way too small. So I tried 11. That seems to work. But I'd rather have 12.

It looks like (to me) the new font selections are not working correctly, but what do I know?

 

[rconn]

Still not reproducible here, regardless of the font size.

Are you using ConPTY tab windows, or the old conhost-style tabs?

Try launching a TCC console session (either in WT or the bare console and doing the DIR there. (It's not clear to me whether your issue is with TCMD or with TCC.)

 

[rconn]

I was able to reproduce your issue on another machine using your TCMD.INI.

The problem is with the Lucida Console font, which is providing the wrong information to DirectWrite about the font ligatures. If you set "TabPtyLigatures=NO" in your TCMD.INI, then Lucida Console should work.

A better solution would be to use a more modern font, like Consolas or Cascadia that has the correct ligature info.

 

[Steven M. Geisler]

I was able to reproduce your issue on another machine using your TCMD.INI.

The problem is with the Lucida Console font, which is providing the wrong information to DirectWrite about the font ligatures. If you set "TabPtyLigatures=NO" in your TCMD.INI, then Lucida Console should work.

A better solution would be to use a more modern font, like Consolas or Cascadia that has the correct ligature info.

Ok. Before I saw your response above, I was trying to do what you asked last night.
So, Lucinda 12 always screws up. 10,11,14,16,20 all worked.
When I started TCC.exe, Lucinda 12 worked.
I'm fine with using Consolas. So we can forget the problem with Lucinda.
BTW, when Lucinda 12 was selected, TakeCommand blew up several times when I tried to add a new tab in the TakeCommand window. Maybe you should remove it.

I do have a question, though. I was using "OPTIONS-STYLES-FONTS to change the font for "Tab Windows". Then I found on OPTIONS-Take Command-Windows" that there are 5 buttons to set fonts. Howerver, I didn't see any change of font in the Take Command window or TCC. What are they used for?

 

[gentzel]

FWIW, I was having issues with JetBrainsMonoNL and ConPTY that I hadn't reported yet and setting "TabPtyLigatures=No" resolved them.

 

[rconn]

I do have a question, though. I was using "OPTIONS-STYLES-FONTS to change the font for "Tab Windows". Then I found on OPTIONS-Take Command-Windows" that there are 5 buttons to set fonts. Howerver, I didn't see any change of font in the Take Command window or TCC. What are they used for?

They are for menu, ribbon, and status bar fonts. The one for "Tab Windows" does change the font in the TCMD tab windows.

 

[rconn]

Ok. Before I saw your response above, I was trying to do what you asked last night.
So, Lucinda 12 always screws up. 10,11,14,16,20 all worked.
When I started TCC.exe, Lucinda 12 worked.

Console sessions don't use ligatures, so the bad values in Lucinda Console wouldn't affect them.

 

[rconn]

FWIW, I was having issues with JetBrainsMonoNL and ConPTY that I hadn't reported yet and setting "TabPtyLigatures=No" resolved them.

The next build (36.52.88, which will be uploaded today) checks the font for bad ligature values and disables them.

 

[gentzel]

The next build (36.52.88, which will be uploaded today) checks the font for bad ligature values and disables them.

Thanks Rex. What surprises me is that the "NL" in JetBrainsMonoNL stands for "No Ligatures" - it's the sans-ligatures version of JetBrainsMono. So confusing that it would have bad ligature values.

EDIT: Removed the setting of "TabPtyLigatures=No" and installed 36.52.88. Worked perfectly.