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

Progress bar rendering new lines when using Hack typeface #158

New Issue
Closed
opened 2026-01-30 21:44:09 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 21:44:09 +00:00
Owner
Copy Link

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

From @mrmckeb on April 17, 2017 8:10

A brief description
When running yarn install I'm seeing a new line for each update to the progress bar. This only happens when I'm not using a default Windows font (I'm using Hack).

Expected results
The progress bar should stay on one line.

Actual results (with terminal output if applicable)
capture

Your Windows build number
1703 / 15063.138 (clean install)

Steps to reproduce the error
I use this script, in a .reg.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont]
"000"="Hack"

Then run yarn install

Obviously I could just not use a custom typeface/font, but that affects my bash usage (there are symbols that default Windows typefaces can't render).

I'm using Hack in this instance, I haven't extensively tested other non-standard fonts. https://github.com/chrissimpkins/hack

This may be related to https://github.com/chrissimpkins/Hack/issues/246. Any help would be appreciated.

Copied from original issue: Microsoft/WSL#1936

Originally created by @bitcrazed on GitHub (Feb 16, 2018). _From @mrmckeb on April 17, 2017 8:10_ **A brief description** When running `yarn install` I'm seeing a new line for each update to the progress bar. This only happens when I'm not using a default Windows font (I'm using Hack). **Expected results** The progress bar should stay on one line. **Actual results (with terminal output if applicable)** ![capture](https://cloud.githubusercontent.com/assets/5043083/25083121/9814ee1a-2398-11e7-8af5-1bfa25131309.PNG) **Your Windows build number** 1703 / 15063.138 (clean install) **Steps to reproduce the error** I use this script, in a .reg. ``` Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Console\TrueTypeFont] "000"="Hack" ``` Then run `yarn install` Obviously I could just not use a custom typeface/font, but that affects my bash usage (there are symbols that default Windows typefaces can't render). I'm using Hack in this instance, I haven't extensively tested other non-standard fonts. https://github.com/chrissimpkins/hack This may be related to https://github.com/chrissimpkins/Hack/issues/246. Any help would be appreciated. _Copied from original issue: Microsoft/WSL#1936_
claunia commented 2026-01-30 21:44:10 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @simonbuchan on April 17, 2017 21:56

I've seen this with most of the fonts available by default in console settings - which ones work?

As a temporary workaround with yarn 0.23, you can add --progress false to ~/.yarnrc

See also https://github.com/yarnpkg/yarn/issues/2530

@bitcrazed commented on GitHub (Feb 16, 2018): _From @simonbuchan on April 17, 2017 21:56_ I've seen this with most of the fonts available by default in console settings - which ones _work_? As a temporary workaround with yarn 0.23, you can add `--progress false` to `~/.yarnrc` See also https://github.com/yarnpkg/yarn/issues/2530
claunia commented 2026-01-30 21:44:10 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @simonbuchan on April 17, 2017 22:9

Did some testing, seems fine in most fonts actually, just broken in the ones I like 😄
Seems to have bad output in "DejaVu Sans Mono" and "Monoid" (I probably still have the hacked version from https://github.com/JB-Dmitry/monoid)
It's fine in Liberation Mono, Source Code Pro, Lucida Console and Consolas, at least.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @simonbuchan on April 17, 2017 22:9_ Did some testing, seems fine in most fonts actually, just broken in the ones I like 😄 Seems to have bad output in "DejaVu Sans Mono" and "Monoid" (I probably still have the hacked version from https://github.com/JB-Dmitry/monoid) It's fine in Liberation Mono, Source Code Pro, Lucida Console and Consolas, at least.
claunia commented 2026-01-30 21:44:10 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @mrmckeb on April 17, 2017 23:41

Thank you @simonbuchan. Hopefully, there's a solution from the Windows console team soon, as I am assuming at this stage that the issue lies there?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @mrmckeb on April 17, 2017 23:41_ Thank you @simonbuchan. Hopefully, there's a solution from the Windows console team soon, as I am assuming at this stage that the issue lies there?
claunia commented 2026-01-30 21:44:10 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on April 20, 2017 16:50

@simonbuchan This looks like it's the same as #1879, but more specifically it's the bug in #1907. Basically, for some fonts, we can't get the size of all unicode characters correctly, and that can lead so strange rendering issues. Just as an example, running tmux and trying to make a vertical split (<prefix> " or split-window -v) with the Hack typeface will most definitely look wrong.

I'll leave this open as one extra node in the large graph of issues related to that bug. I don't think we have a fix planned for that anytime soon, it's a pretty tricky bug that one is.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on April 20, 2017 16:50_ @simonbuchan This looks like it's the same as #1879, but more specifically it's the bug in #1907. Basically, for some fonts, we can't get the size of all unicode characters correctly, and that can lead so strange rendering issues. Just as an example, running tmux and trying to make a vertical split (`<prefix> "` or `split-window -v`) with the Hack typeface will most definitely look wrong. I'll leave this open as one extra node in the large graph of issues related to that bug. I don't think we have a fix planned for that anytime soon, it's a pretty tricky bug that one is.
claunia commented 2026-01-30 21:44:10 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @mrmckeb on April 21, 2017 2:0

Thansk @zadjii-msft. Is there any way to prioritise this issue? I know it seems small, but these sorts of things are always the 'little cuts' that can make adoption a little more painful.

I'm loving using Bash on Windows on a daily basis instead of Bash on macOS, and I'm championing it with co-workers - and these (theming, styling) are the features they often ask about first.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @mrmckeb on April 21, 2017 2:0_ Thansk @zadjii-msft. Is there any way to prioritise this issue? I know it seems small, but these sorts of things are always the 'little cuts' that can make adoption a little more painful. I'm loving using Bash on Windows on a daily basis instead of Bash on macOS, and I'm championing it with co-workers - and these (theming, styling) are the features they often ask about first.
claunia commented 2026-01-30 21:44:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @simonbuchan on April 21, 2017 2:21

Just to mention here this a special case of the general bug as it causes a line-wrap that the escape codes don't know about, which implies the rendered line-wraps and the internal line-wraps (not to be confused with logical, unwrapped lines) are being computed differently.
Does it look like you can prevent the rendered line-wrap from occurring, which would close this bug?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @simonbuchan on April 21, 2017 2:21_ Just to mention here this a special case of the general bug as it causes a line-wrap that the escape codes don't know about, which implies the rendered line-wraps and the internal line-wraps (not to be confused with logical, unwrapped lines) are being computed differently. Does it look like you can prevent the rendered line-wrap from occurring, which would close this bug?
claunia commented 2026-01-30 21:44:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @mateuszlewko on April 23, 2017 20:9

Are there any powerline fonts that work perfectly with tmux? Lucida Console works great but its missing many characters that most themes use.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @mateuszlewko on April 23, 2017 20:9_ Are there any powerline fonts that work perfectly with tmux? Lucida Console works great but its missing many characters that most themes use.
claunia commented 2026-01-30 21:44:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (May 3, 2018):

@mrmckeb: Thanks for filing but if a font is not encoded properly, and doesn't express its glyph metrics correctly, there's not a lot we can do to fix this issue.

We are working on a set of improvements to drastically improve Console's ability to display a MUCH larger range of characters (far more accurately) in the future, but it'll take a few releases to get there.

Your continued patience is appreciated.

@bitcrazed commented on GitHub (May 3, 2018): @mrmckeb: Thanks for filing but if a font is not encoded properly, and doesn't express its glyph metrics correctly, there's not a lot we can do to fix this issue. We are working on a set of improvements to drastically improve Console's ability to display a MUCH larger range of characters (far more accurately) in the future, but it'll take a few releases to get there. Your continued patience is appreciated.
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
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#158
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?