Closed ClusterM closed 2 months ago
Seems more like Windows Terminal bug, actually.
Issue on the Windows Terminal repo: https://github.com/microsoft/terminal/issues/17656
Have you seen #2072 and #2085? Is it the same problem or a different one?
As I see "Right-click on the terminal window", I guess it is also something mouse-related.
@Dazzar56 can you please take a look at this issue?
Have you seen #2072 and #2085? Is it the same problem or a different one?
Seems like it's the same problem, yes.
Answer from Microsoft employee: https://github.com/microsoft/terminal/issues/17656#issuecomment-2266329410
I have bound the clipboard paste action to
Ctrl+Shift+V
in terminal settings. So, I can useCtrl+C
andCtrl+V
to copy and paste text inside FAR, it works fine and doesn't conflict.
Just for reference, how to set it up.
I'm using far2l via Windows Terminal and ssh. I have bound the clipboard paste action to
Ctrl+Shift+V
in terminal settings. So, I can useCtrl+C
andCtrl+V
to copy and paste text inside FAR, it works fine and doesn't conflict.But when I want to paste text from Windows to remote system using
Ctrl+Shift+V
FAR totally freaks out. The text is pasted correctly, but then... FAR stops handling any escape sequences:So, I can't even quit FAR.
Copypasting from remote side to local PC using OSC52 works fine, btw.
upd: Seems like Windows Terminal sends weird escape code sequences. I inspected it.
Steps to reproduce via clean shell:
printf "\x1b[?9001h"
to enable win32-input-modeExpected Behavior
;4;20;116;1;0;1_;4;20;116;0;0;1_;18;101;1;0;1_;18;101;0;0;1_;3;31;115;1;0;1_;3;31;115;0;0;1_;4;20;116;1;0;1_;4;20;116;0;0;1_
It's
t
,e
,s
,t
key presses.Actual Behavior
;0;27;1;0;1_;0;91;1;0;1_;0;50;1;0;1_;0;48;1;0;1_;0;48;1;0;1_;0;126;1;0;1_4;20;116;1;0;1_4;20;116;0;0;1_;18;101;1;0;1_;18;101;0;0;1_3;31;115;1;0;1_3;31;115;0;0;1_4;20;116;1;0;1_4;20;116;0;0;1_;0;27;1;0;1_;0;91;1;0;1_;0;50;1;0;1_;0;48;1;0;1_;0;49;1;0;1_;0;126;1;0;1_
Decoded:
As you can see, there are much more key codes for some reason.