-
Notifications
You must be signed in to change notification settings - Fork 302
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
Windows 10 doesn't register it as monospace type? #4
Comments
We aware if this problem, one of the weights is missing "monospace" tag in metadata. This will be fixed in next update. |
I think this might actually be a lack of Panose flags set - that's what Windows Command Prompt uses to identify monospaced fonts. While it was included in FontLab Studio 5 it did not make FontLab 6 or 7. A separate process/patcher might be required to fix up the ttf after processing. Here's what it looks like in FontLab Studio 5. Toggling this flag is the difference between it showing up in Command Prompt options or not although toggling it does not affect Visual Studio for example. |
I use gVim and it loads monospaced fonts only. same here like cmd or powershell. |
Hello. Is there any time frame for this update? |
if stars will be merciful, the v 1.0.1 will be up in next 8 hours. |
The stars was not so merciful, but we fond the solution. Expect 1.0.1 in Monday. Sorry for the wait. |
Thanks for fixing! Now we can have JetBrains Mono in Windows Command Line, too! 😄 See e.g. this post on how to add fonts to the windows command line font chooser. |
Thank you! 1.0.1 became monospace on Linux. |
The v 1.0.1 is out & it fixing the bug on Win 10. |
Thanks for getting this fixed!! |
Looks like the https://jetbrains.com/mono webpage is still serving the 1.0.0 version when you click the "Download font" button; could someone update that too? |
@dnelson-1901 Thanks for bringing this up. We will update the link after the release of 1.0.2. |
Five hours ago! https://github.com/JetBrains/JetBrainsMono/releases/tag/v1.0.2 |
On my Windows 10 setup, it seems to be registering as a proportional and not monospaced type. For that reason, it won't show up as available font in Command Prompt or Powershell. Other fonts like Fira Code or Inconsolata are fine.
The text was updated successfully, but these errors were encountered: