ProgressBarStyle.ASCII does not print only one line.
See original GitHub issue
and in the case ProgressBarStyle.COLORFUL_UNICODE_BLOCK, block character is ?.

what’s happen to me?
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
java - Print to a specific point in the terminal - Stack Overflow
So what I was thnking about is creating a "checkpiont" in which rewrite the line, but I don't know if that is possible...
Read more >Printer Prints ASCII Codes When Using the Generic/Text Only ...
Your printer may print device (or ASCII) codes when you print using the Generic/Text Only printer driver. Cause. This behavior can occur if...
Read more >Advanced cli progress bars
On a non-dynamic terminal, cli simply prints progress updates as new lines to the screen. Frequently updating the progress in this fashion would...
Read more >Bootstrap Progress Bars - W3Schools
Basic Progress Bar. A progress bar can be used to show a user how far along he/she is in a process. Bootstrap provides...
Read more >R.attr - Android Developers
Whether or not this view is a heading for accessibility purposes. ... Specifies a background drawable for a second stacked row of the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

It seems that
D2Codingdoes not support the block drawing characters. You could use another font that does (and also has CJK support, e.g. https://github.com/be5invis/Sarasa-Gothic)I think the way forward is to include a fix to correctly compute the space of width-2 characters (Hangul / Hiragana / Katakana / Chinese characters / etc.) Thanks for raising this issue! I’ll fix this in a later release, but probably not in the coming few weeks.
Released in version
0.9.1.