We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some powerline symbols do not render.
I'm using starship for my prompt, which leverages powerline font symbols. I'm currently using the Fira Code font.
Here's the proper display in wsltty.
Notice that both the branch symbol before master and the python symbol before v3.6.9.
master
v3.6.9
However, in qterminal, the branch symbol shows but the python symbol does not.
I'm not sure what the solution is, but I assume it's related to some encoding. Here's some tips about powerline symbols not displaying.
cat
The text was updated successfully, but these errors were encountered:
Thank you. Will check it soon.
Sorry, something went wrong.
The fire code font doesn't contains the "SNAKE" glyph, it is provided by Segoe UI Emoji font. You can try merge these font.
I'll check if it is possible to set fallback fonts to support the emojis.
Fira Code was patched to support powerline all the way back in 0.6. I've tried other powerline fonts with the same exact results.
No branches or pull requests
Some powerline symbols do not render.
Expected Behavior
I'm using starship for my prompt, which leverages powerline font symbols. I'm currently using the Fira Code font.
Here's the proper display in wsltty.
Notice that both the branch symbol before
master
and the python symbol beforev3.6.9
.However, in qterminal, the branch symbol shows but the python symbol does not.
Possible Solution
I'm not sure what the solution is, but I assume it's related to some encoding. Here's some tips about powerline symbols not displaying.
Steps to Reproduce (for bugs)
cat
the file.symbols.txt
Context
System Information
The text was updated successfully, but these errors were encountered: