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

font changed after I used less or vim command #13049

New Issue
Closed
opened 2026-01-31 03:32:16 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 03:32:16 +00:00
Owner
Copy Link

Originally created by @zhouzhendiao on GitHub (Mar 16, 2021).

Environment

Windows build number: [Version 10.0.17763.1397]

Steps to reproduce

font changed after I used less or vim command in WSL1

Expected behavior

When I open WSL, the font like this:
image

Actual behavior

But after I used Vim or Less:
the font would change like this:
image

Can Someone tell me the reason?

Originally created by @zhouzhendiao on GitHub (Mar 16, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. ![image](https://user-images.githubusercontent.com/12294679/111242463-2f04c900-863a-11eb-8d83-4adfbc310aaa.png) All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: [Version 10.0.17763.1397] ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> font changed after I used less or vim command in WSL1 # Expected behavior When I open WSL, the font like this: ![image](https://user-images.githubusercontent.com/12294679/111242436-21e7da00-863a-11eb-8e6c-6654419be2fe.png) <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior But after I used Vim or Less: the font would change like this: ![image](https://user-images.githubusercontent.com/12294679/111242469-3330e680-863a-11eb-80ac-34294303773e.png) <!-- What's actually happening? --> Can Someone tell me the reason?
claunia added the Product-ConhostResolution-Duplicate labels 2026-01-31 03:32:16 +00:00
claunia commented 2026-01-31 03:32:17 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Mar 16, 2021):

what is the terminal you are using? Is it cmd.exe? Is it Windows Terminal? You need to give us more.

@skyline75489 commented on GitHub (Mar 16, 2021): what is the terminal you are using? Is it cmd.exe? Is it Windows Terminal? You need to give us more.
claunia commented 2026-01-31 03:32:17 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Mar 16, 2021):

I suspect this might be related to issue #221, although that seems to be triggered by codepage changes, which I wouldn't have thought likely in a WSL shell. But if that is the case, then this is assumedly the GDI renderer and thus conhost. If it turns out he's using Windows Terminal then I have no idea.

@j4james commented on GitHub (Mar 16, 2021): I suspect this might be related to issue #221, although that seems to be triggered by codepage changes, which I wouldn't have thought likely in a WSL shell. But if that is the case, then this is assumedly the GDI renderer and thus conhost. If it turns out he's using Windows Terminal then I have no idea.
claunia commented 2026-01-31 03:32:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 16, 2021):

Version 10.0.17763 ... looks like it might be before WSL used ConPTY for hosting Windows applications. If you end up running the Windows version of vim or less (vim.exe or less.exe), it absolutely may change your codepage. Unavoidable.

@DHowett commented on GitHub (Mar 16, 2021): Version 10.0.17763 ... looks like it _might_ be before WSL used ConPTY for hosting Windows applications. If you end up running the Windows version of vim or less (`vim.exe` or `less.exe`), it absolutely may change your codepage. Unavoidable.
claunia commented 2026-01-31 03:32:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 20, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 20, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 03:32:18 +00:00
Author
Owner
Copy Link

@zhouzhendiao commented on GitHub (Mar 22, 2021):

what is the terminal you are using? Is it cmd.exe? Is it Windows Terminal? You need to give us more.

Just WSL1: ubuntu18.04

@zhouzhendiao commented on GitHub (Mar 22, 2021): > what is the terminal you are using? Is it cmd.exe? Is it Windows Terminal? You need to give us more. Just WSL1: ubuntu18.04
claunia commented 2026-01-31 03:32:18 +00:00
Author
Owner
Copy Link

@zhouzhendiao commented on GitHub (Mar 22, 2021):

I suspect this might be related to issue #221, although that seems to be triggered by codepage changes, which I wouldn't have thought likely in a WSL shell. But if that is the case, then this is assumedly the GDI renderer and thus conhost. If it turns out he's using Windows Terminal then I have no idea.

Thanks for replying, I just used WSL1

@zhouzhendiao commented on GitHub (Mar 22, 2021): > I suspect this might be related to issue #221, although that seems to be triggered by codepage changes, which I wouldn't have thought likely in a WSL shell. But if that is the case, then this is assumedly the GDI renderer and thus conhost. If it turns out he's using Windows Terminal then I have no idea. Thanks for replying, I just used WSL1
claunia commented 2026-01-31 03:32:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 22, 2021):

  • Can you use the console property sheet to show us what the selected fonts are before and after opening vim?
    image -> image

  • Does the font change when you enter vim, then return to the original when you exit?

I'm thinking this is probably the same root cause as #415.

@zadjii-msft commented on GitHub (Mar 22, 2021): * Can you use the console property sheet to show us what the selected fonts are before and after opening vim? ![image](https://user-images.githubusercontent.com/18356694/112008515-8bad2b80-8af3-11eb-9200-3b02ee4e8700.png) -> ![image](https://user-images.githubusercontent.com/18356694/112008573-9b2c7480-8af3-11eb-87e8-cc319cedacb6.png) * Does the font change when you enter vim, then return to the original when you exit? I'm thinking this is probably the same root cause as #415.
claunia commented 2026-01-31 03:32:18 +00:00
Author
Owner
Copy Link

@zhouzhendiao commented on GitHub (Mar 23, 2021):

  • Can you use the console property sheet to show us what the selected fonts are before and after opening vim?
    image -> image
  • Does the font change when you enter vim, then return to the original when you exit?

I'm thinking this is probably the same root cause as #415.

Thanks!
Before opening Vim:
before_vim
After opening Vim:
after_vim

Yeah, font changed from "Consolas" to "新宋体"（Chinese font）

@zhouzhendiao commented on GitHub (Mar 23, 2021): > * Can you use the console property sheet to show us what the selected fonts are before and after opening vim? > ![image](https://user-images.githubusercontent.com/18356694/112008515-8bad2b80-8af3-11eb-9200-3b02ee4e8700.png) -> ![image](https://user-images.githubusercontent.com/18356694/112008573-9b2c7480-8af3-11eb-87e8-cc319cedacb6.png) > * Does the font change when you enter vim, then return to the original when you exit? > > I'm thinking this is probably the same root cause as #415. Thanks! Before opening Vim: ![before_vim](https://user-images.githubusercontent.com/12294679/112076174-e65a8c00-8bb4-11eb-8f76-290b3324553c.png) After opening Vim: ![after_vim](https://user-images.githubusercontent.com/12294679/112076269-1144e000-8bb5-11eb-8b0e-0bcd627560a9.png) Yeah, font changed from "Consolas" to "新宋体"（Chinese font）
claunia commented 2026-01-31 03:32:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 23, 2021):

Yea, this looks exactly like /dup #415

@zadjii-msft commented on GitHub (Mar 23, 2021): Yea, this looks exactly like /dup #415
claunia commented 2026-01-31 03:32:19 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 23, 2021):

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 (Mar 23, 2021): 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 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#13049
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?