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.

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

Automatically support shift-override mouse events #1572

Closed
Screwtapello opened this issue Sep 20, 2018 · 1 comment
Closed

Automatically support shift-override mouse events #1572

Screwtapello opened this issue Sep 20, 2018 · 1 comment

Comments

@Screwtapello
Copy link

I'm currently using Alacritty 63a40df on Debian Testing, with i3 window-manager on X11.

My alacritty.yml contains the default mouse-bindings:

mouse_bindings:
  - { mouse: Middle, action: PasteSelection }

When I'm running a terminal app without mouse support, like bash, a left-click is handled by the terminal and a shift-left click is redundant, but works too.

When I'm running a terminal app with mouse support, like tmux, a left-click is handled by the application and a shift-left click is handled by the terminal, just as I'd expect.

When I'm running a terminal app without mouse support, a middle-click pastes the selection (as configured), and a shift-middle-click does nothing.

When I'm running a terminal app with mouse support, a middle-click is handled by the application and a shift-middle-click still does nothing.

I'm used to always shift-middle-click pasting so I don't have to care whether the running application has mouse support, but this habit brings sadness with Alacritty.

Since mouse-bindings don't allow modifiers anyway, it would be great if Alacritty allowed all mouse bindings to behave like left-click:

  • outside of mouse-reporting mode, clicking does the normal action and shift-clicking does too
  • inside mouse-reporting mode, clicking is reported to the app and shift-clicking does the normal action
@chrisduerr
Copy link
Member

Hey, this is a known issue and a duplicate of #1298. Unfortunately it's a semi-recent regression introduced in #1218. However there already is an open PR which should fix this: #1300.

Regarding the other thing you've mentioned about mouse modifiers, they actually are supported now. However it looks like I forgot to update the configuration file to remove the notice that they are not. I'll spin up a PR to do this later, thanks for the notice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants