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

Emoji in Ubuntu shell are not deleted correctly #8896

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

Originally created by @ivanjonas on GitHub (Jun 8, 2020).

Environment

Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): 1.0.1401.0

Any other software?

Steps to reproduce

  1. Open an Ubuntu/bash window
  2. Note the position of the cursor.
  3. Type the word "git"
  4. Open the Windows emoji picker with Win + period and choose an emoji. For example, the "smiling face with smiling eyes" emoji (😊) or any other emoji that isn't part of the original windows black-and-white emoji set. For contrast, the recycle (♻) emoji does not show this problem because it's part of that set.
  5. Press backspace once to delete the emoji. Notice that the emoji is still visible but the cursor is in the middle of it.
  6. Press backspace again to "finish" deleting the emoji. The original text "git" will still be visible.
  7. Press Enter.

Expected behavior

The git program runs outputting information about subcommands.
If I delete an emoji character that takes up two blocks of space, I expect the cursor to go backward two spaces, and I expect that pressing Enter will execute the command that is displayed.

Actual behavior

The command prompt complains "gi: command not found", even though the line above still says "git"

image

Deleting double-width emoji will move the cursor back only one space, and the displayed command is be the command that will be executed.

Originally created by @ivanjonas on GitHub (Jun 8, 2020). # Environment ```none Windows build number: 10.0.18362.0 Windows Terminal version (if applicable): 1.0.1401.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open an Ubuntu/bash window 2. Note the position of the cursor. 3. Type the word "git" 4. Open the Windows emoji picker with Win + period and choose an emoji. For example, the "smiling face with smiling eyes" emoji (😊) or any other emoji that isn't part of the original windows black-and-white emoji set. For contrast, the recycle (♻) emoji does not show this problem because it's part of that set. 5. Press backspace once to delete the emoji. Notice that the emoji is still visible but the cursor is in the middle of it. 6. Press backspace again to "finish" deleting the emoji. The original text "git" will still be visible. 7. Press Enter. # Expected behavior The `git` program runs outputting information about subcommands. If I delete an emoji character that takes up two blocks of space, I expect the cursor to go backward two spaces, and I expect that pressing Enter will execute the command that is displayed. # Actual behavior The command prompt complains "gi: command not found", even though the line above still says "git" ![image](https://user-images.githubusercontent.com/4935079/83986113-a833fa80-a909-11ea-9d87-93310ec476be.png) Deleting double-width emoji will move the cursor back only one space, and the displayed command is be the command that will be executed.
claunia commented 2026-01-31 01:40:47 +00:00
Author
Owner
Copy Link

@guilhermetod commented on GitHub (Jun 18, 2020):

I see you're using a PowerLine theme. Can you please share the name of it and for which shell? I suggest that you look into the theme's file (e.g. ~/.oh-my-zsh/agnoster.zsh-theme) and see if it's using "literal" emojis (😊) or encoded (\U1F60A or a plugin like emoji[smiling_face_with_smiling_eyes]).

I built a custom theme and had this issue. The problem was in the PowerLine part. It managed to render correctly, but it was badlly encoded and some characters would break it. Not an issue with the terminal.

Edit: For what I see it's relly bash with oh-my-bash, right?

@guilhermetod commented on GitHub (Jun 18, 2020): I see you're using a PowerLine theme. Can you please share the name of it and for which shell? I suggest that you look into the theme's file (e.g. ~/.oh-my-zsh/agnoster.zsh-theme) and see if it's using "literal" emojis (😊) or encoded (\U1F60A or a plugin like emoji[smiling_face_with_smiling_eyes]). I built a custom theme and had this issue. The problem was in the PowerLine part. It managed to render correctly, but it was badlly encoded and some characters would break it. Not an issue with the terminal. Edit: For what I see it's relly bash with oh-my-bash, right?
claunia commented 2026-01-31 01:40:47 +00:00
Author
Owner
Copy Link

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

Hey lemme real quick cross link this with discussion over in #6555, which is seeing some similar disagreement in character width

@zadjii-msft commented on GitHub (Jun 18, 2020): Hey lemme real quick cross link this with discussion over in #6555, which is seeing some similar disagreement in character width
claunia commented 2026-01-31 01:40:47 +00:00
Author
Owner
Copy Link

@ivanjonas commented on GitHub (Jun 18, 2020):

@guilhermetod Heh, you're right, it seems the Windows Terminal came with a powerline out of the box, and it DOES have some issues... but that's a red herring :) I only intended to highlight the difference between the command itself in line 1 ("git") and the interpreted command in line 2 ("gi").

@ivanjonas commented on GitHub (Jun 18, 2020): @guilhermetod Heh, you're right, it seems the Windows Terminal came with a powerline out of the box, and it DOES have some issues... but that's a red herring :) I only intended to highlight the difference between the command itself in line 1 ("git") and the interpreted command in line 2 ("gi").
claunia commented 2026-01-31 01:40:47 +00:00
Author
Owner
Copy Link

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

It looks like we root-caused this in /dup #6555, so I'm gonna close this one out. Thanks everyone for reporting!

@DHowett commented on GitHub (Jun 19, 2020): It looks like we root-caused this in /dup #6555, so I'm gonna close this one out. Thanks everyone for reporting!
claunia commented 2026-01-31 01:40:47 +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-Output Issue-Bug Priority-3 Product-Conhost 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#8896
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?