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
When running a windows command from wsl, the output from the windows command starts over what is already on the wsl terminal, AKA it starts from line 1.
Keyevents are not passed down to the windows process. Ex: pressing Ctrl+C several times doesn't exit the windows process.
Both issues only happen when using wslbridge. If i start wsl by running bash from windows cmd, none of they problems appear. See this screen capture for demonstration.
Notice i'm running both cmd and wsl using conemu. But If i run wslbridge directly by double clicking wslbridge.exe, same issue occurs. Thus i'm pretty sure the bug is in wslbridge, not conemu.
Both issues only happen when using wslbridge. If i start wsl by running
bash
from windows cmd, none of they problems appear. See this screen capture for demonstration.Notice i'm running both cmd and wsl using conemu. But If i run wslbridge directly by double clicking wslbridge.exe, same issue occurs. Thus i'm pretty sure the bug is in wslbridge, not conemu.
https://gfycat.com/dearestcontentgalapagossealion
The text was updated successfully, but these errors were encountered: