starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Win10 stable + pwsh.exe + ssh.exe + mouse events? #537

New Issue
Closed
opened 2026-01-30 21:54:40 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 21:54:40 +00:00
Owner
Copy Link

Originally created by @colemickens on GitHub (Jan 26, 2019).

This bug-tracker is monitored by Windows Console development team and other technical types. We like detail!

If you have a feature request, please post to the UserVoice.

Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible

  • Your Windows build number: Microsoft Windows [Version 10.0.17763.292]

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

Using the latest ssh.exe release (from GitHub as it's usually a bit newer than what's included in Windows 10 builds).

SSH into a remote host. Use tmux/neovim/vim, try to use the mouse in places where it works under usual Linux terminal emulators.

  • What's wrong / what should be happening instead:

This is probably user error on my part, or possibly a feature request, but I can't figure out how to get mouse events to work in this scenario. I feel like it's worked in past incarnations of this computer's windows 10 installs... but maybe that was via WSL?

tl;dr: how can I use my mouse with vim on a remote host using pwsh.exe + ssh.exe from a stable Win10 client?

Thanks!

Originally created by @colemickens on GitHub (Jan 26, 2019). This bug-tracker is monitored by Windows Console development team and other technical types. **We like detail!** If you have a feature request, please post to [the UserVoice](https://wpdev.uservoice.com/forums/266908). > **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible * Your Windows build number: ```Microsoft Windows [Version 10.0.17763.292]``` * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Using the latest ssh.exe release (from GitHub as it's usually a bit newer than what's included in Windows 10 builds). SSH into a remote host. Use tmux/neovim/vim, try to use the mouse in places where it works under usual Linux terminal emulators. * What's wrong / what should be happening instead: This is probably user error on my part, or possibly a feature request, but I can't figure out how to get mouse events to work in this scenario. I feel like it's worked in past incarnations of this computer's windows 10 installs... but maybe that was via WSL? tl;dr: how can I use my mouse with vim on a remote host using pwsh.exe + ssh.exe from a stable Win10 client? Thanks!
claunia added the Resolution-ExternalResolution-Duplicate labels 2026-01-30 21:54:40 +00:00
claunia commented 2026-01-30 21:54:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 26, 2019):

Hey @colemickens! Thanks for the report.
Since you're SSHing to a remote Linux host (I presume based on "places where it works under usual Linux terminal emulators",) that'll be due to PowerShell/Win32-OpenSSH#1310. In short, Win32-OpenSSH is doing its own input translation and is missing out on Console's built-in mouse support.

If you're accessing a Windows host, it's more likely to be because our pty infrastructure doesn't support translating incoming mouse events. If that's the case, I'm happy to repoen this, but we do already have a workitem tracking that on our side. 😄

/cc @manojampalam for the Win32-OpenSSH issue.

@DHowett-MSFT commented on GitHub (Jan 26, 2019): Hey @colemickens! Thanks for the report. Since you're SSHing to a remote Linux host (I presume based on "places where it works under usual Linux terminal emulators",) that'll be due to PowerShell/Win32-OpenSSH#1310. In short, Win32-OpenSSH is doing its own input translation and is missing out on Console's built-in mouse support. If you're accessing a Windows host, it's more likely to be because our pty infrastructure doesn't support translating incoming mouse events. If that's the case, I'm happy to repoen this, but we do already have a workitem tracking that on our side. :smile: /cc @manojampalam for the Win32-OpenSSH issue.
claunia commented 2026-01-30 21:54:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 26, 2019):

Notably, using ssh from within WSL will work for mousing to a remote Linux host.

@DHowett-MSFT commented on GitHub (Jan 26, 2019): Notably, using ssh from within WSL will work for mousing to a remote Linux host.
claunia commented 2026-01-30 21:54:41 +00:00
Author
Owner
Copy Link

@colemickens commented on GitHub (Jan 28, 2019):

Thank you for the detailed answer @DHowett-MSFT and the cross-references to track. Cheers!

@colemickens commented on GitHub (Jan 28, 2019): Thank you for the detailed answer @DHowett-MSFT and the cross-references to track. Cheers!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#537
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?