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

tmux on Windows doesn't respond to mouse events in terminal #29814

Closed
AlteredConstants opened this issue Jun 29, 2017 · 3 comments
Closed

tmux on Windows doesn't respond to mouse events in terminal #29814

AlteredConstants opened this issue Jun 29, 2017 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) WSL Issue when using WSL
Milestone

Comments

@AlteredConstants
Copy link

  • VSCode Version: Code - Insiders 1.14.0-insider (63def6e, 2017-06-28T05:16:57.588Z)
  • OS Version: Windows_NT ia32 10.0.16226
  • Extensions:
Extension Author (truncated) Version
vscode-eslint dba 1.2.11
EditorConfig Edi 0.9.3
prettier-vscode esb 0.20.0
macros ged 1.2.0
vscode-settings-cycler hoo 1.0.1
debugger-for-chrome msj 3.1.6
shell-launcher Tyr 0.1.1

Steps to Reproduce:

  1. Configure VSCode terminal to use a WSL Bash shell on Windows. ("terminal.integrated.shell.windows": "C:\\WINDOWS\\sysnative\\bash.exe")
  2. Open a terminal and run tmux (with set -g mouse on in ~/.tmux.conf).
  3. Output enough text to the terminal to overflow the window.
  4. Attempt to scroll with the mouse.
  5. Open a new panel (Ctrl+B, %).
  6. Attempt to resize the panels with the mouse.
  7. Attempt to focus each panel by clicking within one and then the other with the mouse.

Reproduces without extensions: Yes

Steps 4, 6, and 7 all fail but do work in the normal "Bash on Ubuntu on Windows" terminal outside of VSCode. This is also a problem in 1.13.1. I'd hoped #9958 would fix the problem, but it didn't. (Assuming it made it into the insider build for today?)

@vscodebot vscodebot bot added the insiders label Jun 29, 2017
@vscodebot vscodebot bot added the terminal Integrated terminal issues label Jun 29, 2017
@AlteredConstants
Copy link
Author

Also, before launching tmux, if the regular Bash session has sufficient output to overflow the window, you can scroll. Once you launch tmux, scrolling will show the original shell's scroll buffer (instead of tmux's).

@Tyriar Tyriar added this to the Backlog milestone Jun 29, 2017
@Tyriar Tyriar added the bug Issue identified by VS Code Team member as probable bug label Jun 29, 2017
@weinand weinand added the WSL Issue when using WSL label Aug 16, 2017
@chrmarti chrmarti removed the insiders label Sep 27, 2017
@Tyriar Tyriar added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jan 2, 2018
@Tyriar
Copy link
Member

Tyriar commented Jan 2, 2018

Verified this is still happening. I'm guessing winpty doesn't know to pass through mouse events to the shell

@Tyriar
Copy link
Member

Tyriar commented Sep 12, 2018

This is likely related to winpty, tracking in #45693

@Tyriar Tyriar closed this as completed Sep 12, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 12, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Oct 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) WSL Issue when using WSL
Projects
None yet
Development

No branches or pull requests

4 participants