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

Multi-byte chars not erased correctly by backspace in Git Bash #19805

New Issue
Closed
opened 2026-01-31 06:54:05 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:54:05 +00:00
Owner
Copy Link

Originally created by @ap-axentia on GitHub (May 4, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621.1555

Other Software

Git Bash (Git for Windows), git version 2.40.1.windows.1
Git Bash in Windows Terminal installed with Git for Windows installer checkbox option.

Steps to reproduce

Install Git for Windows, check the box to add it to Windows Terminal.
Open Windows Terminal Git Bash.
Type a character that use more than one byte, eg. £ or ö.
Use backspace to erase the char.

(I am unsure if the issue lies with Windows Terminal or Git for Windows, but I cannot reproduce the same bug in git-bash.exe so that is why I opened the issue here.)

Expected Behavior

The char is erased fully, so that no trace of it is left neither visually nor in the background.

Actual Behavior

The char is erased visually, but something seems to still be left in the background. When pressing backspace again a char of the prompt is removed. Or, if not pressing backspace again, when pressing enter, the response bash: □: command not found is given, where one would expect no response.

image

Originally created by @ap-axentia on GitHub (May 4, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number 10.0.22621.1555 ### Other Software Git Bash (Git for Windows), git version 2.40.1.windows.1 Git Bash in Windows Terminal installed with Git for Windows installer checkbox option. ### Steps to reproduce Install Git for Windows, check the box to add it to Windows Terminal. Open Windows Terminal Git Bash. Type a character that use more than one byte, eg. `£` or `ö`. Use backspace to erase the char. (I am unsure if the issue lies with Windows Terminal or Git for Windows, but I cannot reproduce the same bug in git-bash.exe so that is why I opened the issue here.) ### Expected Behavior The char is erased fully, so that no trace of it is left neither visually nor in the background. ### Actual Behavior The char is erased visually, but something seems to still be left in the background. When pressing backspace again a char of the prompt is removed. Or, if not pressing backspace again, when pressing enter, the response `bash: □: command not found` is given, where one would expect no response. ![image](https://user-images.githubusercontent.com/104353026/236152133-78309703-2d17-4432-8591-5130aaad605e.png)
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 06:54:05 +00:00
claunia commented 2026-01-31 06:54:07 +00:00
Author
Owner
Copy Link

@keith555 commented on GitHub (May 4, 2023):

Sounds similar to #9205

@keith555 commented on GitHub (May 4, 2023): Sounds similar to #9205
claunia commented 2026-01-31 06:54:07 +00:00
Author
Owner
Copy Link

@ap-axentia commented on GitHub (May 4, 2023):

Yes, it sounded very similar to #9205. I tried some more, following the reproduction steps in that issue and in my issue, and I realized that I might have had a messed up git installation, or rather a manual Git Bash addition in Terminal that I confused myself with. So I cannot actually reproduce the problem again. (I had som other issues with git and delta/highlighting therefore I did a lot of experiments.)

So I am actually closing this now, since I believe that a correctly installed and added Git Bash in Windows Terminal actually works. And any remaining issues will be covered by #9205.

@ap-axentia commented on GitHub (May 4, 2023): Yes, it sounded very similar to #9205. I tried some more, following the reproduction steps in that issue and in my issue, and I realized that I might have had a messed up git installation, or rather a manual Git Bash addition in Terminal that I confused myself with. So I cannot actually reproduce the problem again. (I had som other issues with git and delta/highlighting therefore I did a lot of experiments.) So I am actually closing this now, since I believe that a correctly installed and added Git Bash in Windows Terminal actually works. And any remaining issues will be covered by #9205.
claunia commented 2026-01-31 06:54:07 +00:00
Author
Owner
Copy Link

@dktapps commented on GitHub (Oct 20, 2023):

I've had issues with my Git commit messages containing random corrupted characters for almost a year. Turns out it's because " and £ are right next to each other on the British keyboard layout, and backspacing £ leaves a c2 byte, which turns into  when interpreted by bash.

Thank you for writing this issue, you saved me months of misery.

@dktapps commented on GitHub (Oct 20, 2023): I've had issues with my Git commit messages containing random corrupted characters for almost a year. Turns out it's because `"` and `£` are right next to each other on the British keyboard layout, and backspacing `£` leaves a `c2` byte, which turns into `Â` when interpreted by bash. Thank you for writing this issue, you saved me months of misery.
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 Needs-Triage
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#19805
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?