Support PowerLine triangle and diagonal line glyphs
See original GitHub issueVS Code issue showing bad rendering when rendering the glyph from the font: https://github.com/microsoft/vscode/issues/163000
We should support custom rendering of e0b8
through e0bf
powerline symbols:
Code pointer:
Issue Analytics
- State:
- Created 10 months ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Diagonal guide lines - Font Forum - High-Logic
This is a partial solution to the problem of providing guide lines for diagonals. Select a Glyph that you're not going to use...
Read more >Does Terminal.app has Powerline glyph support? - Ask Different
OK got it work. First, install powerline fonts: github.com/powerline/fonts. Then pick one of the fonts, e.g Meslo LG. – anta40.
Read more >Latin square - Wikipedia
In combinatorics and in experimental design, a Latin square is an n × n array filled with n different symbols, each occurring exactly...
Read more >Releases - MonoLisa
On top of the current plans, there are three tiers of subscriptions aimed at business use ... Add support for Powerline terminal glyphs....
Read more >SINUMERIK 840D sl HMI Advanced
SINUMERIK 840D powerline/840DE powerline ... manual by means of a warning triangle, no warning triangle appears ... Explanation of symbols: Function.
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 FreeTop 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
Top GitHub Comments
Really can’t say which route is better one atm. If we switch to wide by default, we might get issues then from broken prompt scripts always emitting the SP hack. (Or even have to place some sanity code in the renderer to detect that condition and to skip the superfluous filler SP on purpose). Idk, maybe lets just stay at the current quirky mode until it causes follow-up issues?
Yep. They not commonly used yet, as they got specced pretty recently (like in current or prev unicode version).