Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Closed
garrettdc opened this issue Nov 6, 2019 · 3 comments
Closed

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

garrettdc opened this issue Nov 6, 2019 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@garrettdc
Copy link

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.
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 6, 2019
@DHowett-MSFT
Copy link
Contributor

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

@ghost
Copy link

ghost commented 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 ghost closed this as completed Nov 6, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Nov 6, 2019
@DHowett-MSFT
Copy link
Contributor

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

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@garrettdc @DHowett-MSFT