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

Disable (or Customize) key to suppress mouse events #4875

Open
carlos-zamora opened this issue Mar 10, 2020 · 5 comments
Open

Disable (or Customize) key to suppress mouse events #4875

carlos-zamora opened this issue Mar 10, 2020 · 5 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal.
Milestone
Backlog

Comments

@carlos-zamora
Copy link
Member

Description of the new feature/enhancement

Work item introduced by #4856. Shift is used to suppress mouse events. A user may want to disable this feature.

If we want to be able to customize it (which I don't think anybody is asking for but I'll include the idea in here anyways), this may be a part of #1553.
@carlos-zamora carlos-zamora added Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Area-Settings Issues related to settings and customizability, for console or terminal Product-Terminal The new Windows Terminal. labels Mar 10, 2020
@ghost ghost added the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Mar 10, 2020
@zadjii-msft
Copy link
Member

I know I'll get corrected if I'm wrong, but from what I recall, shift is pretty universally the "I want the terminal to use this mouse event, not the client app" key. I'm not sure if other terminals let you change that. That's what I can remember about this at least. IIRC there's even some comment in the conhost code about this 😄

@DHowett-MSFT DHowett-MSFT removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Mar 13, 2020
@DHowett-MSFT DHowett-MSFT added this to the Terminal v1.x milestone Mar 13, 2020
@DHowett-MSFT
Copy link
Contributor

Triaged into 1.x.

@carlos-zamora carlos-zamora self-assigned this May 12, 2020
@zadjii-msft zadjii-msft mentioned this issue Aug 9, 2021
Closed
@zadjii-msft
Copy link
Member

The setting as it appears in PuTTY:
image

@zadjii-msft zadjii-msft added good first issue This is a fix that might be easier for someone to do as a first contribution Help Wanted We encourage anyone to jump in on these. labels Aug 9, 2021
@rfc805
Copy link

rfc805 commented Aug 9, 2021

I think it's not described in the initial request, but the comment above to disable the mouse input behavior would be a very useful feature as well. So along with customization and disabling the disable, it would be nice to just have an outright 'off'.

@zadjii-msft zadjii-msft modified the milestones: Terminal Backlog, Backlog Jan 4, 2022
@mspielberg
Copy link

Setting as it appears in Apple Terminal:

image

@zadjii-msft zadjii-msft removed Help Wanted We encourage anyone to jump in on these. good first issue This is a fix that might be easier for someone to do as a first contribution labels Mar 3, 2022
This was referenced Nov 8, 2022
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Product-Terminal The new Windows Terminal.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
6 participants
@mspielberg @carlos-zamora @DHowett-MSFT @zadjii-msft @rfc805 @cinnamon-msft