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

[console]::TreatControlCAsInput or $Host.UI.RawUI.ReadKeynot working correctly in new terminal #3948

New Issue
Closed
opened 2026-01-30 23:33:59 +00:00 by claunia · 1 comment
claunia commented 2026-01-30 23:33:59 +00:00
Owner
Copy Link

Originally created by @tonyt73 on GitHub (Sep 20, 2019).

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0

Steps to reproduce

Test-CTRLC.ps1

[console]::TreatControlCAsInput = $true
Start-Sleep -Seconds 1
$Host.UI.RawUI.FlushInputBuffer()
Do {
    if ($Host.UI.RawUI.KeyAvailable) {
        $Key = [int]$Host.UI.RawUI.ReadKey("AllowCtrlC,IncludeKeyUp,NoEcho").Character
        Write-Host "Key available - $Key"
        if (3 -eq $Key -or  '  ' -eq $Key) {
            [console]::TreatControlCAsInput = $false
            Write-Host "Ctrl-C detected, exiting script..." -ForegroundColor Yellow
            Break
        }
        #$Host.UI.RawUI.FlushInputBuffer()
    }
} While ($true)

Expected behavior

Ctrl+C should be readable from the $Host.UI.RawUI.KeyAvailable and $Host.UI.RawUI.ReadKey functions

Actual behavior

[console]::TreatControlCAsInput = $true Does turn off Ctrl+C
Either $Host.UI.RawUI.KeyAvailable or $Host.UI.RawUI.ReadKey is not working correctly

What works

Start PowerShell console outside of Windows Terminal. aka. standard powershell console window
Run the above style of code and Ctrl+C is detected

Images

PowerShell 6 (x64) Console (works)

image

PowerShell 7 in Windows Terminal

image

Originally created by @tonyt73 on GitHub (Sep 20, 2019). ``` Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 ``` # Steps to reproduce ## Test-CTRLC.ps1 ``` [console]::TreatControlCAsInput = $true Start-Sleep -Seconds 1 $Host.UI.RawUI.FlushInputBuffer() Do { if ($Host.UI.RawUI.KeyAvailable) { $Key = [int]$Host.UI.RawUI.ReadKey("AllowCtrlC,IncludeKeyUp,NoEcho").Character Write-Host "Key available - $Key" if (3 -eq $Key -or ' ' -eq $Key) { [console]::TreatControlCAsInput = $false Write-Host "Ctrl-C detected, exiting script..." -ForegroundColor Yellow Break } #$Host.UI.RawUI.FlushInputBuffer() } } While ($true) ``` # Expected behavior Ctrl+C should be readable from the `$Host.UI.RawUI.KeyAvailable` and `$Host.UI.RawUI.ReadKey` functions # Actual behavior `[console]::TreatControlCAsInput = $true` Does turn off Ctrl+C Either `$Host.UI.RawUI.KeyAvailable` or `$Host.UI.RawUI.ReadKey` is not working correctly # What works Start PowerShell console outside of Windows Terminal. aka. standard powershell console window Run the above style of code and Ctrl+C is detected # Images ## PowerShell 6 (x64) Console (works) ![image](https://user-images.githubusercontent.com/21229341/65292478-f5651600-db9a-11e9-8677-b764c98a3957.png) ## PowerShell 7 in Windows Terminal ![image](https://user-images.githubusercontent.com/21229341/65292520-19c0f280-db9b-11e9-97f2-a16ca2b3ee84.png)
claunia added the Needs-TriageResolution-Duplicate labels 2026-01-30 23:33:59 +00:00
claunia commented 2026-01-30 23:34:00 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 23, 2019):

Looks like a duplicate of #1894.

@DHowett-MSFT commented on GitHub (Sep 23, 2019): Looks like a duplicate of #1894.
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 Needs-Triage 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#3948
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?