You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cmder version: v1.3.24
Operating system: Windows 10 22H2
Cmder Edition
Cmder Full (with Git)
Description of the issue
I connect from cmder using ssh (cmder\vendor\git-for-windows\usr\bin) to the linux server and run midnight commander (mc). And as soon as I press ctrl+o, all the text under mc disappears. This has been happening since git-for-windows 2.27.0.
But I would like to use newer versions of git-for-windows because of the mouse in mc and other graphical improvements.
Can you please advise?
Thank you!
How to reproduce
ssh user@server
run mc
press ctrl+o
text disappears
Additional context
No response
Checklist
I have read the documentation.
I have searched for similar issues and found none that describe my issue.
I have reproduced the issue on the latest version of Cmder.
[] I am certain my issues are not related to ConEmu, Clink, or other third-party tools that Cmder uses.
The text was updated successfully, but these errors were encountered:
Hi, I've done some tests, and it seems that this issue is happening due to ConEmu. Can you please test with some other terminals? Additionally, can you please install the vanilla ConEmu (not with Cmder) and test using the built-in ssh.exe in Windows?
Doing these tests may help us investigate the issue.
Version Information
Cmder Edition
Cmder Full (with Git)
Description of the issue
I connect from cmder using ssh (cmder\vendor\git-for-windows\usr\bin) to the linux server and run midnight commander (mc). And as soon as I press ctrl+o, all the text under mc disappears. This has been happening since git-for-windows 2.27.0.
But I would like to use newer versions of git-for-windows because of the mouse in mc and other graphical improvements.
Can you please advise?
Thank you!
How to reproduce
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: