-
Notifications
You must be signed in to change notification settings - Fork 29
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
JuliaMono's '>' #61
Comments
Can't reproduce on Ubuntu here... If you could find the font, get Info, and tell me what the copyright string says, that might be helpful as a first step. Otherwise, ¯\_(ツ)_/¯ ... |
Sorry, not sure what information you were asking for. |
If you find the font file that you're using (I don't know where you put it), click on it, a window pops up and says at the top right [Info | Installed]. In Info, you should be able to see come information strings, such as Copyright... |
Ah okay, thanks.
The terminal is GNOME Terminal version |
That's more or less what I have here (GNOME terminal 3.28.2) - so the problem is only on your setup, somehow. I can't do any troubleshooting on Linux, so I'll just have to leave this issue open as unresolved. Is it a problem for you in Julia too? |
Yea, looks like that no matter the application in the terminal (julia, vim etc). If you have any further tips on how to debug this I am happy to try. The character I see is the ligature version for |
You're picking up a glyph that used by the ligature for To be honest, a lot of the problems people have with fonts are due to problems with terminal software. If you look at tonsky's repo (eg tonsky/FiraCode#162) there are many examples where fonts are rendered incorrectly and the likely suspect is the terminal. Of course, the authors of terminal software will say it's a problem with the font... The places where fonts tend to work without errors most often are the browsers - so much work has gone into text display. And even they have problems... So one possible way out is to strip out the ligatures from the file. Here's my first attempt at making a version that has no ligatures or alternates. JuliaMono-RegularPlain-20201011-1239.ttf.zip If you try it out, watch out for font caching - it can be difficult to persuade an OS to let go of a font and update it... |
Thanks.
Yea, this version works (perhaps that is obvious since the problematic glyphs are not included 🙂 ). Would it be possible to distribute the font without alternates like this? Otherwise, is there a tool I can run myself on the font to strip out alternates? |
I can add this to the build process so that it's automatically added to the repo. So, like the Latin versions, there could be a RegularPlain and BoldPlain version. For now, you could try |
I can reproduce the problem in gnome-terminal on Ubuntu 16.04. But Ubuntu 16.04 is ancient (I used a Docker image to reproduce the bug). It works fine on Ubuntu 20.04 (gnome-terminal 3.36.2). |
Thanks. Good to know! I know I should upgrade... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
For reference, this is what I am using to (succesfully) strip the font from any ligatures and such:
|
This is what

<>
looks like in my terminal:but it looks correct in e.g. SublimeText and elsewhere. This is on Ubuntu (16.04) with the standard terminal.
Ps. I just installed JuliaMono and it looks great for everything else, thanks!
The text was updated successfully, but these errors were encountered: