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

I can't use square brackets in windows terminal if I use ssh connection #6504

Closed
smirnova-anv opened this issue Jun 14, 2020 · 5 comments
Closed
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.

Comments

@smirnova-anv
Copy link

smirnova-anv commented Jun 14, 2020

Hello!
I have this problem, what do I do wrong?

I open windows terminal, in it I can use signs: [ ] and #.
Then I open ssh connection with my virtual machine (Virtual Box, Linux, Fedora 30, Ssh-Server, also docker is running in it). And while ssh-connection works, I can not use signs [ ] and # neither in terminal, neither in nano / vim.

I have tried:
change leanguage
sudo dnf update
sudo dnf nano upgrade
Nothing works.

Please, how can I use [ ] and # in Windows Terminal while I use ssh-connection?
I use Windows 10 x64 prof 1909 version

Thx

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 14, 2020
@zadjii-msft
Copy link
Member

zadjii-msft commented Jun 15, 2020

What ssh client are you using? ssh from WSL, ssh.exe that's built in to Windows, or maybe some other version?

What's the output of echo $TERM and infocmp while ssh'd in to the VM?

What keyboard layout are you using?

Which version of the Terminal?

@zadjii-msft zadjii-msft added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Product-Terminal The new Windows Terminal. labels Jun 15, 2020
@smirnova-anv
Copy link
Author

For strange way it works now!
Thank you, guys!

@ghost ghost added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jun 17, 2020
@DHowett
Copy link
Member

DHowett commented Jun 17, 2020

That is very strange. Thanks for following up! I'll close this out, but please let me know if it comes back.

@DHowett DHowett removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Jun 17, 2020
@DHowett DHowett closed this as completed Jun 17, 2020
@DHowett DHowett added the Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely. label Jun 17, 2020
@VitalyArtemiev
Copy link

VitalyArtemiev commented Jun 22, 2020

@DHowett
I have the same problem. All symbols in Windows Terminal work fine. I ssh to a debian-based system (tried Ubuntu and Raspbian), and lose ability to type symbols, like ` ~ < > { } [ ] @ # $ etc.
Some of the symbols I'm having trouble with require Shift, some don't, like ` or [ ].
I can input % & * without any problem.

Using powershell or cmd through Terminal doesn't make a difference, both fail to send these symbols. If I use ssh through plain old cmd shell or powershell without Windows Terminal, everything works fine.

Pasting symbols doesn't work either. It's not a visual glitch, the symbols are not there after typing into a file, saving, and opening through another shell. I also have WSL installed, I have no trouble typing these symbols into Ubuntu there, so ssh is somehow involved in the problem.

I've found a possibly related problem here: microsoft/WSL#11
Also this seems to describe the same problem: #5878
It's marked as fixed, but seems to resurface once in a while.
Some of the users mentioned pressing alt+[ . This works, after I press alt + [, I can input one of the above mentioned symbols.

I've tried messing with locale, it appeared to work for a while after I set localectl VC keymap to "us-intl", but stopped working soon after, and I can't repeat this result.

I am using a regular USB keyboard with a standard RU layout, my windows system uses 2 languages - RU and EN-US. I've tried all combinations of layouts and locales I can think of on the systems I'm trying to ssh to.

Edit: I installed Windows Terminal Preview (was unable to do so before), seems like the problem is absent here.

@Zigman13
Copy link

Zigman13 commented Jun 23, 2020

Same for me, after ssh.exe (powershell) to ubuntu system i type shift + 4 to achieve $ char.
nothing happens there. not char printing.
on centos 6 another server seems all is fine.
infocmp for that machine(ubuntu is):

Reconstructed via infocmp from file: /lib/terminfo/x/xterm-256color

xterm-256color|xterm with 256 colors,
am, bce, ccc, km, mc5i, mir, msgr, npc, xenl,
colors#0x100, cols#80, it#8, lines#24, pairs#0x7fff,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=\r,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=\n, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dim=\E[2m,
dl=\E[%p1%dM, dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K,
el1=\E[1K, flash=\E[?5h$<100/>\E[?5l, home=\E[H,
hpa=\E[%i%p1%dG, ht=^I, hts=\EH, ich=\E[%p1%d@,
il=\E[%p1%dL, il1=\E[L, ind=\n, indn=\E[%p1%dS,
initc=\E]4;%p1%d;rgb:%p2%{255}%%{1000}%/%2.2X/%p3%{255}%%{1000}%/%2.2X/%p4%{255}%*%{1000}%/%2.2X\E\,
invis=\E[8m, is2=\E[!p\E[?3;4l\E[4l\E>, kDC=\E[3;2~,
kEND=\E[1;2F, kHOM=\E[1;2H, kIC=\E[2;2~, kLFT=\E[1;2D,
kNXT=\E[6;2~, kPRV=\E[5;2~, kRIT=\E[1;2C, kb2=\EOE, kbs=^?,
kcbt=\E[Z, kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\EOP, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf13=\E[1;2P, kf14=\E[1;2Q,
kf15=\E[1;2R, kf16=\E[1;2S, kf17=\E[15;2~, kf18=\E[17;2~,
kf19=\E[18;2~, kf2=\EOQ, kf20=\E[19;2~, kf21=\E[20;2~,
kf22=\E[21;2~, kf23=\E[23;2~, kf24=\E[24;2~,
kf25=\E[1;5P, kf26=\E[1;5Q, kf27=\E[1;5R, kf28=\E[1;5S,
kf29=\E[15;5~, kf3=\EOR, kf30=\E[17;5~, kf31=\E[18;5~,
kf32=\E[19;5~, kf33=\E[20;5~, kf34=\E[21;5~,
kf35=\E[23;5~, kf36=\E[24;5~, kf37=\E[1;6P, kf38=\E[1;6Q,
kf39=\E[1;6R, kf4=\EOS, kf40=\E[1;6S, kf41=\E[15;6~,
kf42=\E[17;6~, kf43=\E[18;6~, kf44=\E[19;6~,
kf45=\E[20;6~, kf46=\E[21;6~, kf47=\E[23;6~,
kf48=\E[24;6~, kf49=\E[1;3P, kf5=\E[15~, kf50=\E[1;3Q,
kf51=\E[1;3R, kf52=\E[1;3S, kf53=\E[15;3~, kf54=\E[17;3~,
kf55=\E[18;3~, kf56=\E[19;3~, kf57=\E[20;3~,
kf58=\E[21;3~, kf59=\E[23;3~, kf6=\E[17~, kf60=\E[24;3~,
kf61=\E[1;4P, kf62=\E[1;4Q, kf63=\E[1;4R, kf7=\E[18~,
kf8=\E[19~, kf9=\E[20~, khome=\EOH, kich1=\E[2~,
kind=\E[1;2B, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
kri=\E[1;2A, mc0=\E[i, mc4=\E[4i, mc5=\E[5i, meml=\El,
memu=\Em, oc=\E]104\007, op=\E[39;49m, rc=\E8,
rep=%p1%c\E[%p2%{1}%-%db, rev=\E[7m, ri=\EM,
rin=\E[%p1%dT, ritm=\E[23m, rmacs=\E(B, rmam=\E[?7l,
rmcup=\E[?1049l\E[23;0;0t, rmir=\E[4l, rmkx=\E[?1l\E>,
rmm=\E[?1034l, rmso=\E[27m, rmul=\E[24m,
rs1=\Ec\E]104\007, rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7,
setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
sgr=%?%p9%t\E(0%e\E(B%;\E[0%?%p6%t;1%;%?%p5%t;2%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m,
sgr0=\E(B\E[m, sitm=\E[3m, smacs=\E(0, smam=\E[?7h,
smcup=\E[?1049h\E[22;0;0t, smir=\E[4h, smkx=\E[?1h\E=,
smm=\E[?1034h, smso=\E[7m, smul=\E[4m, tbc=\E[3g,
u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?%[;0123456789]c,
u9=\E[c, vpa=\E[%i%p1%dd,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Tag-Fix Doesn't match tag requirements Product-Terminal The new Windows Terminal. Resolution-No-Repro We couldn't get this to happen, or it stopped happening entirely.
Projects
None yet
Development

No branches or pull requests

5 participants