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

print of 'ls' is not utf-8 (gitbash in wt) #7262

New Issue
Closed
opened 2026-01-31 00:59:24 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 00:59:24 +00:00
Owner
Copy Link

Originally created by @yobome on GitHub (Apr 3, 2020).

Issues

I added git bash in wt:

image

and when I input ls, then:

image

but when I open git bash (not using wt), it uses utf8:
image

how can I fix it?

Environment

Windows build number: windows10 1909 (10.0.18363.752)
Windows Terminal version (if applicable): 0.10.781.0

Originally created by @yobome on GitHub (Apr 3, 2020). # Issues I added git bash in wt: ![image](https://user-images.githubusercontent.com/26548120/78368177-cc1b4d00-75f5-11ea-9ba0-dcbdba1ad4c0.png) and when I input ls, then: ![image](https://user-images.githubusercontent.com/26548120/78368619-785d3380-75f6-11ea-8c95-399232506d3f.png) but when I open git bash (not using wt), it uses utf8: ![image](https://user-images.githubusercontent.com/26548120/78368721-a3e01e00-75f6-11ea-9dca-78c436c5d2b6.png) how can I fix it? # Environment Windows build number: windows10 1909 (10.0.18363.752) Windows Terminal version (if applicable): 0.10.781.0
claunia added the Issue-QuestionNeeds-Tag-FixResolution-AnsweredProduct-Terminal labels 2026-01-31 00:59:25 +00:00
claunia commented 2026-01-31 00:59:26 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 3, 2020):

What is TERM, LANG, LC_ALL set to when running git bash in the Windows Terminal? What are their values when running in git bash directly?

What commandline are you providing for git bash in your profiles.json?

@zadjii-msft commented on GitHub (Apr 3, 2020): What is `TERM`, `LANG`, `LC_ALL` set to when running git bash in the Windows Terminal? What are their values when running in git bash directly? What `commandline` are you providing for git bash in your `profiles.json`?
claunia commented 2026-01-31 00:59:26 +00:00
Author
Owner
Copy Link

@yobome commented on GitHub (Apr 3, 2020):

How to check them? "echo $LC_ALL" doesn't work.

the value of commandline : "commandline": "D:\Git\bin\bash.exe"

@yobome commented on GitHub (Apr 3, 2020): How to check them? "echo $LC_ALL" doesn't work. the value of commandline : "commandline": "D:\\Git\\bin\\bash.exe"
claunia commented 2026-01-31 00:59:26 +00:00
Author
Owner
Copy Link

@yobome commented on GitHub (Apr 3, 2020):

OK, I edit "bash.bashrc" in "%GITHOME%/Git/etc/".

add two lines in the tail:
export LANG="zh_CN.UTF-8"
export LC_ALL="zh_CN.UTF-8"

and it works.

thanks for your help!

@yobome commented on GitHub (Apr 3, 2020): OK, I edit "bash.bashrc" in "%GITHOME%/Git/etc/". add two lines in the tail: export LANG="zh_CN.UTF-8" export LC_ALL="zh_CN.UTF-8" and it works. thanks for your help!
claunia commented 2026-01-31 00:59:26 +00:00
Author
Owner
Copy Link

@yobome commented on GitHub (Apr 3, 2020):

but I still wonder why it works when I use git bash directly......

@yobome commented on GitHub (Apr 3, 2020): but I still wonder why it works when I use git bash directly......
claunia commented 2026-01-31 00:59:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 3, 2020):

Try changing your commandline to end with bash.exe -li

@DHowett-MSFT commented on GitHub (Apr 3, 2020): Try changing your commandline to end with `bash.exe -li`
claunia commented 2026-01-31 00:59:27 +00:00
Author
Owner
Copy Link

@yobome commented on GitHub (Apr 3, 2020):

Try changing your commandline to end with bash.exe -li

it works!

What does "-li" mean?

@yobome commented on GitHub (Apr 3, 2020): > Try changing your commandline to end with `bash.exe -li` it works! What does "-li" mean?
claunia commented 2026-01-31 00:59:27 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 3, 2020):

-li means --login and --interactive. They're two important arguments to make sure that Bash gets started up in the right configuration. The git-for-windows folks let us know that we were missing it in our config example 😄

@DHowett-MSFT commented on GitHub (Apr 3, 2020): `-li` means `--login` and `--interactive`. They're two important arguments to make sure that Bash gets started up in the right configuration. The git-for-windows folks let us know that we were missing it in our config example :smile:
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-Question Needs-Tag-Fix Product-Terminal Resolution-Answered
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#7262
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?