Mouse not working on Windows
I'm runing vim in Windows 10 using the WSL Ubuntu installation.
In Terminus, set mouse=a does not seem to enable mouse controls. However, in the Windows cmd console it works (obviously after typing bash).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks unless you comment. Thank you for your contributions.
Not stale, am seeing this behaviour currently in alpha 54
Thanks @wolf99. Only stale because no one has worked on it.
I also just tried it again yesterday and was planning to raise the issue.
Scrolling the terminal window also does not work.
@Eugeny -- any hope for this?
At this moment, this seems to be a winpty issue - it's not forwarding mouse events to the actual windows console underneath. This should be fixed once ConPTY support lands in winpty: https://github.com/Microsoft/node-pty/issues/216
It looks like ConPTY support is now in winpty 0.80 and 0.81: https://github.com/Microsoft/node-pty/commit/cce934f48eafa4e02033f76c909589723ccb9e29
Great! Any idea when the connection will happen in terminus?
@bewing @abalter looks like that still isn't enough as ConPTY itself swallows mouse events before they can get to node-pty: https://github.com/Microsoft/console/issues/376
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks unless you comment. Thank you for your contributions.
Any updates on this? Mouse clicks and scrolls still seem to be unregistered on WSL (Ubuntu 18.04).
Still no mouse support in ConPTY: https://github.com/microsoft/terminal/issues/376
Windows Terminal got mouse support recently, but they rely on private conhost.exe APIs instead of ConPTY.
I'm using Windows 10 Insider dev channel. Strangely mouse support worked like a charm on build 20190 (with conpty enabled) but stopped working when I updated to build 20197 today.
It looks like mouse support in ConPTY finally dropped with version 1.9 of Terminal in May: https://github.com/microsoft/terminal/issues/376#issuecomment-849756080
Mouse support does not appear to be working in work tabby 1.0.152 with Terminal version 1.9.1942 (at least trying with vim and mouse=a). I guess additional work will be needed to hook things up now?
Windows Terminal ships with its own complete bleeding edge implementation of ConPTY (including an own conhost.exe) - I'm not sure how much work would be involved in importing and integrating it into node-pty and what Microsoft's roadmap is for bringing those changes into the conhost that ships with Windows.
So I just noticed that mouse support is working in Tabby 1.0.158 with WSL (Pengwin/WLinux) on Windows 11. I don't think mouse support works on the same Tabby version on my Windows 10 machine, so I'm guessing that Microsoft finally ported the changes into conhost on Windows 11.
Can confirm mouse support is not working in windows 10 as the latest release. I happen to be in the process of upgrading to win11 now, so if I remember I'll report back here to see if it changed anything.
@Qix- did this end-up working ? Trying out tabby right now, and wondering if my issues with the mouse are related to Win10 too :)
I didn't upgrade to 11 after all, but yeah it seems that is the case. Which is strange because windows terminal supports the mouse. So you'd think it'd be possible.
Windows Terminal is currently shipping its own version of conhost.exe and ConPTY API, which are different from what is available in the OS. I've looked at integrating these in Tabby but it looks like a ton of work :/
still dont working
Are there any updates on this problem? Maybe some workarounds?
I'm very upset about not being able to use neovim with Tabby :(
The issue was spotted 5 yrs ago and seems it still hasn't been addressed. At least not from my end☹️