starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

can't type symbols like | <> @ ^ #8016

New Issue
Closed
opened 2026-01-31 01:18:41 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 01:18:41 +00:00
Owner
Copy Link

Originally created by @fiber-optics on GitHub (May 8, 2020).

Hi, i use Microsoft Windows NT 10.0.18363.0
Terminal version - 0.11.1251.0

when i type in powershell | <> ^ @ - its typing, all goods, but when i run
ssh myhost
and try type again symbols like | <> @ ^
it's not typing, not showing, i can't even paste it's, if i copy thats symbols.

but if i run just power shell(not in terminal, single app) - all good.

Originally created by @fiber-optics on GitHub (May 8, 2020). Hi, i use Microsoft Windows NT 10.0.18363.0 Terminal version - 0.11.1251.0 when i type in powershell | <> ^ @ - its typing, all goods, but when i run ssh myhost and try type again symbols like | <> @ ^ it's not typing, not showing, i can't even paste it's, if i copy thats symbols. but if i run just power shell(not in terminal, single app) - all good.
claunia added the Issue-BugArea-InputResolution-ExternalProduct-Terminal labels 2026-01-31 01:18:41 +00:00
claunia commented 2026-01-31 01:18:42 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 8, 2020):

What keyboard layout are you using? What version of ssh?

@zadjii-msft commented on GitHub (May 8, 2020): What keyboard layout are you using? What version of `ssh`?
claunia commented 2026-01-31 01:18:42 +00:00
Author
Owner
Copy Link

@fiber-optics commented on GitHub (May 8, 2020):

keyboard layout us-102
OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5

@fiber-optics commented on GitHub (May 8, 2020): keyboard layout us-102 OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
claunia commented 2026-01-31 01:18:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 8, 2020):

Alright here's another question that might be able to narrow this issue down - if you use ssh from a WSL distro, do those keys work?

@zadjii-msft commented on GitHub (May 8, 2020): Alright here's another question that might be able to narrow this issue down - if you use `ssh` from a WSL distro, do those keys work?
claunia commented 2026-01-31 01:18:43 +00:00
Author
Owner
Copy Link

@fiber-optics commented on GitHub (May 8, 2020):

Alright here's another question that might be able to narrow this issue down - if you use ssh from a WSL distro, do those keys work?

i don't try. any wsl distro not install currently

@fiber-optics commented on GitHub (May 8, 2020): > Alright here's another question that might be able to narrow this issue down - if you use `ssh` from a WSL distro, do those keys work? i don't try. any wsl distro not install currently
claunia commented 2026-01-31 01:18:43 +00:00
Author
Owner
Copy Link

@fiber-optics commented on GitHub (May 10, 2020):

i install wsl ubuntu 20.04, all symbols works perfect.
but in powershell from win terminal still not working

@fiber-optics commented on GitHub (May 10, 2020): i install wsl ubuntu 20.04, all symbols works perfect. but in powershell from win terminal still not working
claunia commented 2026-01-31 01:18:44 +00:00
Author
Owner
Copy Link

@touuki commented on GitHub (May 10, 2020):

I can type these symbol |<>@^, but when I type symbols like … — ‧, it has exactly the same problem. Work fine on wsl and standalone powershell, but cannot work on ssh or telnet from terminal.

@touuki commented on GitHub (May 10, 2020): I can type these symbol `|<>@^`, but when I type symbols like `… — ‧`, it has exactly the same problem. Work fine on wsl and standalone powershell, but cannot work on ssh or telnet from terminal.
claunia commented 2026-01-31 01:18:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 10, 2020):

@touuki those symbols are not in the standard CP437 symbol plane, so Windows Telnet will never support them, and Windows SSH has a bug right now that makes them not work. This has been resolved in the 8.x releases. 😄

@DHowett-MSFT commented on GitHub (May 10, 2020): @touuki those symbols are not in the standard CP437 symbol plane, so _Windows Telnet_ will never support them, and Windows SSH has a bug right now that makes them not work. This has been resolved in the 8.x releases. :smile:
claunia commented 2026-01-31 01:18:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 10, 2020):

This sounds like a Win32-OpenSSH bug.

@fiber-optics, if you install Win32-OpenSSH 8.x from their releases page, does it work?

@DHowett-MSFT commented on GitHub (May 10, 2020): This sounds like a Win32-OpenSSH bug. @fiber-optics, if you install Win32-OpenSSH 8.x from [their releases page](https://github.com/PowerShell/Win32-OpenSSH/releases), does it work?
claunia commented 2026-01-31 01:18:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 11, 2020):

Resolving external for now.

@DHowett-MSFT commented on GitHub (May 11, 2020): Resolving external for now.
claunia commented 2026-01-31 01:18:44 +00:00
Author
Owner
Copy Link

@touuki commented on GitHub (May 11, 2020):

@DHowett-MSFT Oh, yeah. It works fine in OpenSSH_for_Windows_8.1p1, thanks.

@touuki commented on GitHub (May 11, 2020): @DHowett-MSFT Oh, yeah. It works fine in OpenSSH_for_Windows_8.1p1, thanks.
claunia commented 2026-01-31 01:18:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 11, 2020):

I'm happy to hear that!

@DHowett-MSFT commented on GitHub (May 11, 2020): I'm happy to hear that!
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 Area-Input Issue-Bug Product-Terminal 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#8016
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?