Windows Terminal does not pass mouse events to WSL 2 #4836

Closed
opened 2026-01-30 23:57:43 +00:00 by claunia · 3 comments
Owner

Originally created by @garrettdc on GitHub (Nov 6, 2019).

Environment

Windows build number: 10.0.19008.0
Windows Terminal version: 0.6.2951.0
WSL 2: Ubuntu 19.04

Steps to reproduce

  • Open terminal
  • Open file to edit in vim
  • Type ':set mouse=a' to enable mouse mode globally
  • Attempt to scroll

Expected behavior

  • Scrolling and other mouse events should be passed through and handled by the respective program
  • Double clicking should engage VISUAL mode in vim

Actual behavior

  • Scrolling causes the terminal to scroll into it's scrollback buffer
    windows_terminal_vim_scroll
  • Double clicking selects text in the terminal, but not in the application itself. This seems more in line with how I would expect single click and drag or shift + click events to be handled.
Originally created by @garrettdc on GitHub (Nov 6, 2019). # Environment ```none Windows build number: 10.0.19008.0 Windows Terminal version: 0.6.2951.0 WSL 2: Ubuntu 19.04 ``` # Steps to reproduce * Open terminal * Open file to edit in vim * Type ':set mouse=a' to enable mouse mode globally * Attempt to scroll # Expected behavior * Scrolling and other mouse events should be passed through and handled by the respective program * Double clicking should engage VISUAL mode in vim # Actual behavior * Scrolling causes the terminal to scroll into it's scrollback buffer ![windows_terminal_vim_scroll](https://user-images.githubusercontent.com/13264485/68268359-737e5e80-001b-11ea-8b2a-3b9de40bebe9.png) * Double clicking selects text in the terminal, but not in the application itself. This seems more in line with how I would expect single click and drag or shift + click events to be handled.
claunia added the Resolution-Duplicate label 2026-01-30 23:57:43 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Nov 6, 2019):

/dup #376, #545, #531, #2056, #2344, #2364, #2727, #3046, #3364, #3450

@DHowett-MSFT commented on GitHub (Nov 6, 2019): /dup #376, #545, #531, #2056, #2344, #2364, #2727, #3046, #3364, #3450
Author
Owner

@ghost commented on GitHub (Nov 6, 2019):

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 (Nov 6, 2019): 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!
Author
Owner

@DHowett-MSFT commented on GitHub (Nov 6, 2019):

(please make sure you search before submitting a new issue! thanks!)

@DHowett-MSFT commented on GitHub (Nov 6, 2019): (please make sure you search before submitting a new issue! thanks!)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4836