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

Ctrl+Space in Powershell Core produces double quote character #8962

New Issue
Closed
opened 2026-01-31 01:42:28 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:42:28 +00:00
Owner
Copy Link

Originally created by @jwefers on GitHub (Jun 10, 2020).

Environment

Windows build number:  10.0.19041.0
Windows Terminal version (if applicable): 1.0.1402.0 (Preview from Store)
Locale: ENG language, DE keyboard (German)

Any other software?
Powershell Core 7.0.1, 7.1.0-preview.3

Steps to reproduce

Having a german keyboard, open PowerShell Core in Windows Terminal. Start with e.g. Get-, then Ctrl+Space.

Also, do the same for normal Windows Powershell 5.1.xxx

Expected behavior

The autocomplete Menu as it works in normal Powershell terminal shows up.

Actual behavior

In PS Core: double quote character is typed
In PS: nothing happens, but apparently, the terminal (? console host?) is registering something, as if i repeat it rapidly, the cursor does not blink but stays until i stop
(In WSL, also nothing happens, also registers something)

Originally created by @jwefers on GitHub (Jun 10, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.0.1402.0 (Preview from Store) Locale: ENG language, DE keyboard (German) Any other software? Powershell Core 7.0.1, 7.1.0-preview.3 ``` # Steps to reproduce Having a german keyboard, open PowerShell Core in Windows Terminal. Start with e.g. `Get-`, then Ctrl+Space. Also, do the same for normal Windows Powershell 5.1.xxx # Expected behavior The autocomplete Menu as it works in normal Powershell terminal shows up. # Actual behavior In PS Core: double quote character is typed In PS: nothing happens, but apparently, the terminal (? console host?) is registering something, as if i repeat it rapidly, the cursor does not blink but stays until i stop (In WSL, also nothing happens, also registers something)
claunia added the Issue-BugArea-InputResolution-DuplicateProduct-Conpty labels 2026-01-31 01:42:29 +00:00
claunia commented 2026-01-31 01:42:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 16, 2020):

I'm hoping this will just magically go away with all the work that's been done for #4999 in Terminal 1.1.

@zadjii-msft commented on GitHub (Jun 16, 2020): I'm hoping this will just magically go away with all the work that's been done for #4999 in Terminal 1.1.
claunia commented 2026-01-31 01:42:30 +00:00
Author
Owner
Copy Link

@jwefers commented on GitHub (Jun 16, 2020):

Ah, i read that thread and what made me open this defect was your remark:
image
that is should already be fixed

@jwefers commented on GitHub (Jun 16, 2020): Ah, i read that thread and what made me open this defect was your remark: ![image](https://user-images.githubusercontent.com/851823/84796513-fe372b00-aff8-11ea-8e1a-732278b77733.png) that is should already be fixed
claunia commented 2026-01-31 01:42:31 +00:00
Author
Owner
Copy Link

@jwefers commented on GitHub (Jun 16, 2020):

What i just discover: The very same issue (" being typed), happens in the VS Code terminal:
image

not your turf probably but coincidence?

@jwefers commented on GitHub (Jun 16, 2020): What i just discover: The very same issue (`"` being typed), happens in the VS Code terminal: ![image](https://user-images.githubusercontent.com/851823/84796940-861d3500-aff9-11ea-8d0c-86e102d87aaa.png) not your turf probably but coincidence?
claunia commented 2026-01-31 01:42:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 19, 2020):

So, this is definitely our turf (unfortunately!). We own the translation layer that VSCode is using, and it's the same one as in Windows Terminal.

Ctrl+Space gets encoded as NUL, and on the receiving end we ... translate that to Ctrl+Shif+2

Powershell treats this the same as Shift+2.

So, a little more info about terminals.

The don't really communicate in keys and modifiers and all that. They communicate in control characters or character sequences start are introduced with U+001B ESCAPE. Unfortunately, a number of different keys map to the same thing.

NUL is one of those encodings with multiple keys. Ctrl+Space and Ctrl+Shift+2 both encode to the same byte. When we try to go back from "byte" to "what keys was the user pressing at the time" we get the wrong one.

We cannot fix this in the general case. However, we recently landed #4999 which improves the fidelity of keyboard input for all consumers (opt-in!) by giving them raw access to the literal keys that were pressed.

With 4999, and with Terminal preview 1.1, Ctrl+Space comes out as Ctrl+Space and Ctrl+Shift+2 comes out as Ctrl+Shift+2.

/dup #4999

😄

@DHowett commented on GitHub (Jun 19, 2020): So, this is definitely our turf (unfortunately!). We own the translation layer that VSCode is using, and it's the same one as in Windows Terminal. <kbd>Ctrl+Space</kbd> gets encoded as `NUL`, and on the receiving end we ... translate that to <kbd>Ctrl+Shif+2</kbd> Powershell treats this the same as <kbd>Shift+2</kbd>. So, a little more info about terminals. The don't really communicate in keys and modifiers and all that. They communicate in control characters or character sequences start are introduced with `U+001B ESCAPE`. Unfortunately, a number of different keys map to the same thing. `NUL` is one of those encodings with multiple keys. <kbd>Ctrl+Space</kbd> and <kbd>Ctrl+Shift+2</kbd> both encode to the same byte. When we try to go back from "byte" to "what keys was the user pressing at the time" we get the wrong one. We **cannot fix this** in the general case. However, we recently landed #4999 which improves the fidelity of keyboard input for all consumers (opt-in!) by giving them raw access to the literal keys that were pressed. With 4999, and with Terminal preview 1.1, Ctrl+Space comes out as Ctrl+Space and Ctrl+Shift+2 comes out as Ctrl+Shift+2. /dup #4999 :smile:
claunia commented 2026-01-31 01:42:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 19, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jun 19, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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-Conpty 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#8962
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?