-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Usage of bidi characters caused mangled display #2774
Comments
If I understand this right, then this is a problem with Nerd Fonts version 2 that is fixed with version 3. (See ryanoasis/nerd-fonts#478.) Lazygit now supports version 3 (only on master, not in the latest release, sorry), so if you could try if this fixes the issue, this would be appreciated. |
No, it's not a font issue. The bidi behaviour is triggered by any right-to-left character, regardless of its glyph. |
Or does the change mean that RTL characters are not used anymore? |
Yes, I know. NerdFonts is a system where existing fonts are extended with many icons. The issue was that NerdFonts v2 chose a range of code points for some of these icons that overlapped with some existing hebrew ranges. In v3 those code points were moved to an used range. |
For anybody that wanders into this issue after unexpectedly seeing these shin characters in lieu of the expected icons, I post my scenario for posterity. At some point, the cask for nerd-fonts updated Victor Mono from v2 to v3. Probably it happened at the same time as the others, but I would only notice with Victor Mono. As a result, my my lazygit started to look a bit wonky. The solution that @stefanhaller implemented resolves this, but in case it isn't immediately clear how, you must add |
According to mintty/wsltty#336, lazygit seems to use some Hebrew characters (like שׂ ,שּׁ) for layout or as markers.
Since right-to-left script characters cause display to be reordered in a proper bidi way on terminals that support it,
this totally spoils any pane formatting. Please do not use bidi.
The text was updated successfully, but these errors were encountered: