Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Powerline glyph not rendering correctly #2184

Open
ghost opened this issue Oct 7, 2020 · 3 comments
Open

Powerline glyph not rendering correctly #2184

ghost opened this issue Oct 7, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Oct 7, 2020

Versions

ConEmu build: 191012 preview x64
OS version: Windows 10 x64
Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): zsh on WSL (Ubuntu)

Problem description

When using ConEmu with this font, powerline glyphs get displayed incorrectly.

Steps to reproduce

  1. Use this command to output the symbol: bash -c "echo -e '\\uE0B2\\uE0B0'"

Actual results

Using ConEmu with WSL (without bridge):
image

Expected results

Using Ubuntu WSL directly (same fonts installed):
image

Additional files

My Settings

@cpkio
Copy link

cpkio commented Sep 3, 2021

This is not WSL issue, its ConEmu renderer bug. I'm using bare Windows 10, just CMD/Powershell. ConEmu renderer substitutes some glyphs, even if they exist in the font. I've made a special version of a bitmap font I use to demonstrate the issue (see a hole in 0xE0B0 powerline glyph on the left).

Here in the screenshot I show output of 0xE0B0 in ConEmu latest (left), and in Windows GDI Neovim GUI (Nvy) (right).
2021-09-03_120950

Windows GDI GUI has no problem displaying the glyph as it is, but ConEmu for some reason substitutes this with a vector version from somewhere. On the next picture it is obvious, that ConEmu renderer uses vector font on 0xE0B0 & 0xE0B2, and 0xE0B1 & 0xE0B3 are rendered from a raster font (you see the building blocks for 0xE0B1 & 0xE0B3):
2021-09-03_122427

@cpkio
Copy link

cpkio commented Sep 3, 2021

I have to say this may not be ConEmu problem. I found out that prepending 0xE0B0 with regular non-space symbols like ' or letters will result in displaying the character in the font, not the vector glyph from nowhere. Also, joining 0xE0B0 & 0xE0B2 or 0xE0B2 & 0xE0B0 will result in triangle ligatures, that aren't in the original font. Probably this can be avoided with changing the rendering method. See also microsoft/terminal#10930

@Vampire
Copy link

Vampire commented Apr 28, 2023

I think this is basically a duplicate of #703 because ConEmu does not properly support the used font features and hopefully the fix for that issue will also fix this if it ever comes. But I guess by then I switched to Windows Terminal. :-/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants