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

Handle mouse events #26

Closed
placeybordeaux opened this issue Mar 28, 2017 · 3 comments
Closed

Handle mouse events #26

placeybordeaux opened this issue Mar 28, 2017 · 3 comments

Comments

@placeybordeaux
Copy link

It's possible it's user error on my part, but I don't seem to see any of the mouse events going through and don't see anything in the docs that suggest this feature is intentionally absent.

@kennylevinsen
Copy link

kennylevinsen commented Jun 30, 2017

Mouse events are enabled by a special xterm-extension command, equivalent to doing echo -e '\x1b[?1002h\x1b[?1006h'.

abduco doesn't know that this is enabled, so when an application enables it, the user detach, and later reattach, the state is lost, despite having worked properly in the beginning.

I added the above echo command to my "work" script that connects to nvim (same script ends with "tput reset" to avoid odd terminal state).

Alternatively, make the application reapply its mouse setup. In vim, this can be done by doing :set mouse= followed by :set mouse=a

@placeybordeaux
Copy link
Author

So this could be handled like "alternative_buffer" is handled?

@martanne
Copy link
Owner

This is a known limitation, see #32.

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

No branches or pull requests

3 participants