-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Paste with Ctrl removes leading special character in SSH #17264
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Closed similar issues:
|
Thanks for the report! I'm sorry that we haven't been able to reproduce this yet. I just gave it a try with 1.22 (Canary) in zsh and bash over ssh, one of which supports bracketed paste mode and the other of which does not. Would you be able to test this out in the Canary channel/? |
Hi, I tested it again using following version: The Problem stays the same. I have learned a few things though:
In case the remote host is Debian 12, pasting works without the brackets being removed, except when pasting a password in the password mask. Since there were some updates, this is the current version I'm using: 1.20.11781.0 |
Does this repro if you use ssh within WSL /? |
Windows Terminal version
1.20.11271.0
Windows build number
10.0.22631.0
Other Software
openssh-client/jammy-security,now 1:8.9p1-3ubuntu0.6
Steps to reproduce
Connect to remote Linux server via SSH using WSL or Powershell.
Paste a string starting with one of these characters
[]{}
usingCtrl+Shift+v
,Ctrl+v
orCtrl+ Right Click
.Example:
[rlkdjf[]{}dt
Expected Behavior
Complete String gets pasted into the Shell.
Actual Behavior
Leading character and the second character are removed from the String.
Using
Shift+Insert
orRight Click
does not remove the leading characters.This has worked until the latest update (winget package). I'm assuming this is form the 1.20 update.
The text was updated successfully, but these errors were encountered: