New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input can entirely stop functioning after following guide for Bash/WSL-Bridge #1311
Comments
Hopefully most recent commit fixed this? As per #1314 and build 171109 I'm unable to reproduce this for my state: ConEmu (build 171109-64) {Bash:bash} task with following command:
|
Build 171117 has been released. |
ConEmu build: 180528 (preview) I am still getting this issue. Console freezes randomly and stops processing input. This happens a lot, especially when scrolling/pasting. |
I have no idea what's happening |
Maximus, on the latest Windows insider builds, Conemu is having cygwin rendering problems with the connector + wslbridge. However, conemu + mintty + wslbridge is working fine. It is having serious rendering problems like problems with caret positioning and buffer corruption. |
Details please, in the new issue. |
Versions
ConEmu build: 171025(Alpha)/x64
OS version: Windows 10 x64
Used shell version : WSL + WSLBridge, as outlined in the WSL guide
Problem description
While using the shell, input will randomly stop working. This happens much more often than it would otherwise while in vim- simply scrolling has a huge chance to entirely kill input. I know that it's not a total freeze because the UI still updates (clock, blinking cursor, and uptime), but updates are no longer received from the keyboard. Ctrl + C, Ctrl + Q, Esc, etc do nothing to make the keyboard function again. This can happen at any time with any application open (or not open).
Steps to reproduce
To reproduce quickly and reliably, do the following:
Actual results
Input dies
Expected results
Input should not die
Additional files
[Settings]https://my.mixtape.moe/bauija.xml
[logs]https://my.mixtape.moe/ofljku.zip
The text was updated successfully, but these errors were encountered: