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

lazygit #11357

New Issue
Closed
opened 2026-01-31 02:45:27 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:45:27 +00:00
Owner
Copy Link

Originally created by @xaotag on GitHub (Nov 12, 2020).

terminal
image
powershell
image

Originally created by @xaotag on GitHub (Nov 12, 2020). terminal ![image](https://user-images.githubusercontent.com/40427877/98924822-38f1b080-2510-11eb-988e-c05d7c2ee82d.png) powershell ![image](https://user-images.githubusercontent.com/40427877/98924944-6179aa80-2510-11eb-8812-fa6d2177be47.png)
claunia added the Needs-TriageResolution-ExternalNeeds-Tag-FixTracking-External labels 2026-01-31 02:45:28 +00:00
claunia commented 2026-01-31 02:45:29 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Nov 12, 2020):

I think this is a known issue in lazygit, which doesn't fully support full-width characters (see https://github.com/jesseduffield/lazygit/issues/24). Apparently the problem was partially fixed in PR 231, so upgrading lazygit may help if you're using an old version.

In your PowerShell screenshot there aren't any Chinese characters visible, which is probably why you aren't seeing the issue there. It would be useful for comparison purposes if you could show the exact same diff in both Windows Terminal and PowerShell.

It would also be useful if you said which version of Windows Terminal you're using as well as the version of lazygit that you're using.

@j4james commented on GitHub (Nov 12, 2020): I think this is a known issue in lazygit, which doesn't fully support full-width characters (see https://github.com/jesseduffield/lazygit/issues/24). Apparently the problem was partially fixed in [PR 231](https://github.com/jesseduffield/lazygit/pull/231), so upgrading lazygit may help if you're using an old version. In your PowerShell screenshot there aren't any Chinese characters visible, which is probably why you aren't seeing the issue there. It would be useful for comparison purposes if you could show the exact same diff in both Windows Terminal and PowerShell. It would also be useful if you said which version of Windows Terminal you're using as well as the version of lazygit that you're using.
claunia commented 2026-01-31 02:45:29 +00:00
Author
Owner
Copy Link

@xaotag commented on GitHub (Nov 12, 2020):

如果你使用旧版本，升
look
image

@xaotag commented on GitHub (Nov 12, 2020): > 如果你使用旧版本，升 look ![image](https://user-images.githubusercontent.com/40427877/98944420-f9d15880-252b-11eb-9f17-0a3e1d603165.png)
claunia commented 2026-01-31 02:45:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 12, 2020):

Alright so this sounds like it's an external issue with lazygit, thanks for digging up the upstream issue @j4james!

@zadjii-msft commented on GitHub (Nov 12, 2020): Alright so this sounds like it's an external issue with lazygit, thanks for digging up the upstream issue @j4james!
claunia commented 2026-01-31 02:45:29 +00:00
Author
Owner
Copy Link

@xaotag commented on GitHub (Nov 14, 2020):

in the cmd
image

@xaotag commented on GitHub (Nov 14, 2020): in the cmd ![image](https://user-images.githubusercontent.com/40427877/99150530-3c339a80-26d0-11eb-972f-8dcceac06e4c.png)
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-Tag-Fix Needs-Triage Resolution-External Tracking-External
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#11357
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?