Mouse actions are not forwarded to git bash #14970

Closed
opened 2026-01-31 04:24:38 +00:00 by claunia · 7 comments
Owner

Originally created by @numEricL on GitHub (Aug 25, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

Git bash, mintty 3.5.0 (x86_64-pc-msys) [Windows 18363]

Steps to reproduce

Add git bash to wt and launch (command line is "%PROGRAMFILES%\git\bin\bash.exe" --login -i -l)
Open vim and enable mouse vim -u NONE -c "set mouse=a"
Attempt to scroll

Expected Behavior

Vim to capture mouse inputs

Actual Behavior

Mouse inputs are handled by wt, e.g. scrolling affects the wt buffer.

Originally created by @numEricL on GitHub (Aug 25, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software Git bash, mintty 3.5.0 (x86_64-pc-msys) [Windows 18363] ### Steps to reproduce Add git bash to wt and launch (command line is `"%PROGRAMFILES%\git\bin\bash.exe" --login -i -l`) Open vim and enable mouse `vim -u NONE -c "set mouse=a"` Attempt to scroll ### Expected Behavior Vim to capture mouse inputs ### Actual Behavior Mouse inputs are handled by wt, e.g. scrolling affects the wt buffer.
claunia added the Resolution-Duplicate label 2026-01-31 04:24:38 +00:00
Author
Owner

@numEricL commented on GitHub (Aug 25, 2021):

Similar issues have been posted before, but these are before issue #376. I'm able to use wt with wsl and have mouse events forwarded as expected, so the problem seems specific to git bash. Git bash without wt however handles mouse events as expected.

@numEricL commented on GitHub (Aug 25, 2021): Similar issues have been posted before, but these are before issue #376. I'm able to use wt with wsl and have mouse events forwarded as expected, so the problem seems specific to git bash. Git bash without wt however handles mouse events as expected.
Author
Owner

@DHowett commented on GitHub (Aug 25, 2021):

Which version of vim are you running? I suspect that it is smarter than the average bear, but not quite smart enough yet; see https://github.com/microsoft/terminal/issues/10321#issuecomment-855083607 for more info.

If vim is using VT sequences instead of Win32 APIs (which it should be doing owing to being hosted in Cygwin), scrolling should certainly work... but if it's falling back on the win32 APIs, it shouldn't support it even outside of Terminal. 🤔

@DHowett commented on GitHub (Aug 25, 2021): Which version of vim are you running? I suspect that it is smarter than the average bear, but not quite smart enough yet; see https://github.com/microsoft/terminal/issues/10321#issuecomment-855083607 for more info. If vim is using VT sequences instead of Win32 APIs (which it should be doing owing to being hosted in Cygwin), scrolling _should_ certainly work... but if it's falling back on the win32 APIs, it shouldn't support it even outside of Terminal. 🤔
Author
Owner

@numEricL commented on GitHub (Aug 25, 2021):

VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jul 25 2021 21:26:36)
Included patches: 1-3182
Compiled by https://www.msys2.org/

Nice table! I don't think git bash has any cygwin dependencies and instead runs on top of mingw, is that incorrect?

I find that mouse input works as expected when running vim from cygwin inside and outside of wt.

@numEricL commented on GitHub (Aug 25, 2021): VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Jul 25 2021 21:26:36) Included patches: 1-3182 Compiled by <https://www.msys2.org/> Nice table! I don't think git bash has any cygwin dependencies and instead runs on top of mingw, is that incorrect? I find that mouse input works as expected when running vim from cygwin inside and outside of wt.
Author
Owner

@DHowett commented on GitHub (Aug 25, 2021):

cygwin ... mingw

Alas, the MSYS runtime is a fork of the Cygwin runtime! 😄

This is a really useful data point. Thank you!

@DHowett commented on GitHub (Aug 25, 2021): > cygwin ... mingw Alas, the MSYS runtime is a fork of the Cygwin runtime! :smile: This is a really useful data point. Thank you!
Author
Owner

@zadjii-msft commented on GitHub (May 16, 2022):

@DHowett wait, does this mean this one is in fact a dupe, or not?

@zadjii-msft commented on GitHub (May 16, 2022): @DHowett wait, does this mean this one is in fact a dupe, or not?
Author
Owner

@DHowett commented on GitHub (May 16, 2022):

I believe it is! Thanks!

/dup #10321

@DHowett commented on GitHub (May 16, 2022): I believe it is! Thanks! /dup #10321
Author
Owner

@ghost commented on GitHub (May 16, 2022):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (May 16, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14970