ConEmu 220418 preview terminal gets stuck at 80 usable columns

[coleman-rik]

ConEmu build: 220418 preview x64 OS version: Windows 10 Pro x64 Used shell version: git-bash, cmd, powershell

Problem description

Far more often than should happen, when using ConEmu to launch a ssh session from powershell to a Linux server the number of usable columns reverts to a hard 80.

Typically I have my window set to 160 columns. I have 160 usable columns in both powershell and my ssh session. Then I'll enter a command (what it is doesn't matter, ls will do it) and it starts to wrap at 80 columns.

No matter what I do I am stuck at 80 usable columns. The window may list 160 or 100, or 180 it doesn't matter, windows larger than 80 just display lots of unusable blank space after the 80th column. Neither resizing the window manually, nor using the setting dialog corrects the issue. It changes the windows size just fine, but the usable number of columns is fixed at 80.

If I exit the ssh session, the underlying powershell session is also locked at 80 columns. Apparently, the only way to fix the issue is to close all ConEmu windows. Closing just the problematic window doesn't help. Needless to say, when you have half a dozen to a dozen ssh sessions having to close everything just to clear this issue is more than a little painful.

Opening a new ConEmu window is usually enough to clear the issue, until inevitably it randomly returns.

Is there some way to stop this from happening, or at least fix it without having to completely close down all open ConEmu windows?

Thanks.

[Maximus5]

• Do you mean by "wrap" that the size of the window is still 160, but lines are wrapped at 80'th column?
• What if you open RealConsole at that moment?
• Which ssh version do you use? There are a lot of binaries (openshh/msys/cygwin/...) Do you use a connector to run ssh?

[coleman-rik]

Sorry that it's been a couple of days.

• Yes. If I have a window that's 160 columns wide, or any number larger than 80, the lines all wrap at the 80th column.
• Just a miniaturized version of what the main console shows.
• The default ssh client in Windows 10 Pro x64. No connector used. I usually launch from a PowerShell prompt, but I have also tried from the Cmd prompt with no difference.

I hope that that helps.

[Maximus5]

As you don't use connector, I'm afraid it's an OpenSSH (which you use most probably) bug. I can recommend to try cygwin ssh with connector or run it directly.

[coleman-rik]

Are you sure? Recently I've switched to WSL (which is using OpenSSH) and cmd as well as Powershell and CMD directly and none of these methods exhibit the same behavior.

To reiterate:

• If I use native PowerShell and ssh no problems
• If I use native Cmd and ssh no problems
• If I use ConEmu with PowerShell and ssh intermittent problems
• If I use ConEmu with Cmd and ssh intermittent problems

Seems unlikely in that case that the issue is the underlying ssh command. Wouldn't you agree?

[Maximus5]

Yeah, I cannot guarantee it's not a conemu bug. AnsiLogs will help a lot to investigate https://conemu.github.io/en/AnsiLogFiles.html