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

Add mouse support #3364

Closed
cascer1 opened this issue Oct 29, 2019 · 2 comments
Closed

Add mouse support #3364

cascer1 opened this issue Oct 29, 2019 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@cascer1
Copy link

cascer1 commented Oct 29, 2019

Description of the new feature/enhancement

Currently it seems like the terminal doesn't pass mouse events to WSL (for example to select text in visual mode in vim). I would like to be able to continue using my mouse inside WSL.
@cascer1 cascer1 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 29, 2019
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 29, 2019
@zadjii-msft
Copy link
Member

Thanks for the report! Mouse input doesn't work correctly in the Windows Terminal currently. That's being tracked by a pair of issues: #545 and #376. Once both of those are done, mouse input will work in the Terminal again.

/dup #376
/dup #545 #2727 #2344 #2364 #2056 #1975

@ghost
Copy link

ghost commented Oct 29, 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 Oct 29, 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 Oct 29, 2019
@DHowett-MSFT DHowett-MSFT mentioned this issue Nov 6, 2019
Closed
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
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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
@cascer1 @zadjii-msft