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

Issue with Entering Standalone Diacritic Characters - Data Loss Risk #21279

New Issue
Closed
opened 2026-01-31 07:38:30 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 07:38:30 +00:00
Owner
Copy Link

Originally created by @mjkno on GitHub (Feb 20, 2024).

Windows Terminal version

1.20.10303.0

Windows build number

10.0.19045.3930

Other Software

WSL2 2.0.9.0, Ubuntu 20.04.6, zsh 5.8 (x86_64-ubuntu-linux-gnu), GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)

Steps to reproduce

  1. Open Linux session on Windows Terminal.
  2. Attempt to input a standalone diacritic character by pressing the corresponding dead key followed by the spacebar. For example, to enter "~", one would press the "~" key followed by space.

Expected Behavior

The terminal should output the diacritic character itself when the dead key is followed by a spacebar press, as per the standard input method on European keyboards. For instance, pressing "~" followed by space should result in "~".

Actual Behavior

Instead of displaying the intended diacritic character, the terminal outputs a space character " ". This behavior diverges from the norm and does not occur with other diacritics in the terminal; for example, pressing "~" followed by "a" correctly produces "ã".

The issue affects the input of all standalone diacritic characters via dead keys, impacting the standard functionality of keyboards with diacritic support.

This issue may have critical implications for command-line operations, particularly in Unix/Linux environments. A notable example is the command rm *~, which is commonly used to delete backup files created by text editors. Due to the bug, the intended command is altered to rm *, which could inadvertently lead to the deletion of all files in the directory, posing a significant risk of critical data loss.

Originally created by @mjkno on GitHub (Feb 20, 2024). ### Windows Terminal version 1.20.10303.0 ### Windows build number 10.0.19045.3930 ### Other Software WSL2 2.0.9.0, Ubuntu 20.04.6, zsh 5.8 (x86_64-ubuntu-linux-gnu), GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) ### Steps to reproduce 1. Open Linux session on Windows Terminal. 2. Attempt to input a standalone diacritic character by pressing the corresponding dead key followed by the spacebar. For example, to enter "\~", one would press the "\~" key followed by space. ### Expected Behavior The terminal should output the diacritic character itself when the dead key is followed by a spacebar press, as per the standard input method on European keyboards. For instance, pressing "\~" followed by space should result in "\~". ### Actual Behavior Instead of displaying the intended diacritic character, the terminal outputs a space character " ". This behavior diverges from the norm and does not occur with other diacritics in the terminal; for example, pressing "\~" followed by "a" correctly produces "ã". The issue affects the input of all standalone diacritic characters via dead keys, impacting the standard functionality of keyboards with diacritic support. This issue **may have critical implications** for command-line operations, particularly in Unix/Linux environments. A notable example is the command `rm *~`, which is commonly used to delete backup files created by text editors. Due to the bug, the intended command is altered to `rm *`, which could inadvertently lead to the deletion of all files in the directory, posing a significant risk of critical data loss.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:38:30 +00:00
claunia commented 2026-01-31 07:38:31 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 21, 2024):

Thanks for filing. Good news! This was fixed in WT Canary by #16645. We'll backport it soon.
/dup #16641

@carlos-zamora commented on GitHub (Feb 21, 2024): Thanks for filing. Good news! This was fixed in WT Canary by #16645. We'll backport it soon. /dup #16641
claunia commented 2026-01-31 07:38:32 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Feb 21, 2024):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Feb 21, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Issue-Bug 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#21279
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?