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

windows touch keyboard works incorrectly in WSL #504

New Issue
Open
opened 2026-01-30 21:53:57 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 21:53:57 +00:00
Owner
Copy Link

Originally created by @ns740 on GitHub (Jan 6, 2019).

  • My Windows build number:
    Microsoft Windows [Version 10.0.17134.472]

  • What i'm doing and what's happening:

Originally I reported this as a WSL issue but i'm moving here in response to
this reply from @therealkenc here:
https://github.com/Microsoft/WSL/issues/2483#issuecomment-451708681

I am using a Surface Pro 4 in tablet mode, running Ubuntu [Ubuntu 16.04.5 LTS] in WSL.

Various things that work correctly with an attached hardware keyboard fail to work correctly with the touch keyboard. For example:

  1. entering a password (containing an uppercase character) when prompted after a "sudo ls" command in bash (and clicking "ENTER" after typing the unechoed password).
    In this case the password is rejected even when i am "extra sure" i am typing the correct password.
  2. editing a file in vim and then attempting to exit by typing these keystrokes:
    [ESC] : q [SHIFT] 1
    ([SHIFT] 1 is the way to type the "!" character on the touch keyboard)
    in this case (unlike 1 above) there is visible evidence of strange behavior because the expected echoed command at the bottom of the vim screen is
    :q!
    BUT it actually is
    :q^@!
    my version of vim doesn't mind the extra "^@" and executes the exit command anyway but this is a way to get visual confirmation of the unexpected keyboard behavior
  3. from a bash prompt enter:
    tmux
    [CTRL] b [SHIFT] "             
    (to open a new tmux pane below the the current pane)
    using the touch keyboard displays """ instead of opening a new pane as expected

Notes

  1. if instead of using the windows 10 touch keyboard, I use the osk.exe "Onscreen Keyboard" the problem does not occur. (In example 1 above, hitting [ENTER] after typing the correct password works as expected. In example 2, ":q!" appears in the vim command line as expected and in example 3 the pane opens as expected)
  2. if instead of using the windows 10 touch keyboard to type the password in example 1, the password is copied to the windows clipboard and pasted into the console window (using a longpress - the touch equivalent of a right-click) the password is accepted as expected
Originally created by @ns740 on GitHub (Jan 6, 2019). * My Windows build number: `Microsoft Windows [Version 10.0.17134.472]` * What i'm doing and what's happening: Originally I reported this as a WSL issue but i'm moving here in response to this reply from @therealkenc here: [https://github.com/Microsoft/WSL/issues/2483#issuecomment-451708681](https://github.com/Microsoft/WSL/issues/2483#issuecomment-451708681) I am using a Surface Pro 4 in tablet mode, running Ubuntu [Ubuntu 16.04.5 LTS] in WSL. Various things that work correctly with an attached hardware keyboard fail to work correctly with the touch keyboard. For example: 1. entering a password (containing an uppercase character) when prompted after a "sudo ls" command in bash (and clicking "ENTER" after typing the unechoed password). In this case the password is rejected even when i am "extra sure" i am typing the correct password. 2. editing a file in vim and then attempting to exit by typing these keystrokes: `[ESC] : q [SHIFT] 1` (`[SHIFT] 1` is the way to type the "!" character on the touch keyboard) in this case (unlike 1 above) there is visible evidence of strange behavior because the expected echoed command at the bottom of the vim screen is `:q!` BUT it actually is `:q^@!` my version of vim doesn't mind the extra "`^@`" and executes the exit command anyway but this is a way to get visual confirmation of the unexpected keyboard behavior 3. from a bash prompt enter: `tmux` `[CTRL] b [SHIFT] "`              _(to open a new tmux pane below the the current pane)_ using the touch keyboard displays "`"`" instead of opening a new pane as expected **Notes** 1. if instead of using the windows 10 touch keyboard, I use the `osk.exe` "Onscreen Keyboard" the problem does not occur. (In example 1 above, hitting `[ENTER`] after typing the correct password works as expected. In example 2, "`:q!`" appears in the vim command line as expected and in example 3 the pane opens as expected) 2. if instead of using the windows 10 touch keyboard to type the password in example 1, the password is copied to the windows clipboard and pasted into the console window (using a longpress - the touch equivalent of a right-click) the password is accepted as expected
claunia added the Resolution-Duplicate label 2026-01-30 21:53:57 +00:00
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
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#504
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?