Option + Select does not work

[konsalex]

What Operating System(s) are you seeing this problem on?

macOS

Which Wayland compositor or X11 Window manager(s) are you using?

Just MacOS

WezTerm version

wezterm 20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

Lazydocker requires Option+Dragging to select the text to be copied. This works in iTerm but not in Wezterm

To Reproduce

Run lazydocker and try to copy logs

Configuration

no config

Expected Behavior

Press option + drag the mouse cursor to copy the test

Logs

No response

Anything else?

[bew]

Wezterm uses Shift by default to bypass mouse reporting, allowing you to select arbitrary text.

You can change it to Option if you want with the bypass_mouse_reporting_modifiers config ;)

Something like this in your own config should do the trick:

config.bypass_mouse_reporting_modifiers = "OPT"

[konsalex]

@bew indeed, but then there is another problem. Not sure exactly what is causing this, or if I should update the title to reflect this better.

https://github.com/user-attachments/assets/895e6ee7-8079-41e2-b0b7-81bd4e2fac57

[bew]

Does it also happen with default setting (using shift) ?

I don't know much about macOS so won't be able to help you on that.

[konsalex]

@bew yes it happens with the default

[wez]

if the region holding the selection is re-drawn by the application, the selection is cleared. If the program you are using is constantly updating the output, you won't be able to select the text in that region until it stops (or you stop it using CTRL-S/CTRL-Q to stop/resume the program. Your stty settings control those key assignments).

[github-actions[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.