search

warpdotdev / Warp

Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.
https://warp.dev
Other
21.28k stars 370 forks source link

control over mouse reporting #1114

Closed jcourteau closed 2 years ago

jcourteau commented 2 years ago

Discord username (optional)

No response

Describe the solution you'd like?

The equivalent of the iterm "mouse reporting" options; controlling whether the mouse clicks and scroll wheel events are passed through to terminal apps, or ignored. This would be a toggle-able option, ideally with 2 separate options for clicks vs mouse wheel events, just like iterm.

This would allow people to ignore mouse clicks, and use the OS-level drag-to-select / right click menu / etc; which I find a heck of a lot more useful for cross-application interaction (highlight a thing in an SSH session, CMD-C, over to IDE, CMD-V, etc)

Is your feature request related to a problem? Please describe.

With the current setup, mouse clicks are passed through to things like vim, so when you try to highlight / copy / paste text with the mouse, instead you get vim's visual mode / select / etc.

This is useful to a lot of folks! But I (and probably a few others) prefer it the other way.

Additional context

No response

gagata commented 2 years ago

hey! I think you can disable it in vim specifically by running set mouse-=a

mind pointing where this config option is in iterm?

jcourteau commented 2 years ago

🤦 I didn't even think to check vim-specific settings; I'm not surprised they have this specific combo featured. It works exactly how I'm used to, too.

In iterm2, the settings I mentioned are at:

  1. session menu ->
  2. edit session ... menu item ->
  3. terminal tab ->
  4. terminal emulation section ->
  5. enable mouse reporting and its 2 sub-options

It can also be accessed via the iterm2 menu, preferences, profiles,