macos: not detected as a monospace font #26
Comments
|
It seems that IntelliJ also does not recognise it as a monospace font. There is an article on their support page here: https://intellij-support.jetbrains.com/hc/en-us/articles/360000068140 that says it can have something to do with it not including a bold version. |
IdreesInc
added
the
potential-bug
|
Problem is due to #77. I'm having a bit of difficulty trying to determine how to emulate the character replacement that fonts like FiraCode use to get around this problem so I will likely need external help there. Let me know if this causes any problems with using the font. |
IdreesInc
added
bug
br3ndonland
added a commit
to br3ndonland/dotfiles
that referenced
this issue
Oct 13, 2024
This commit will update `kitty.conf` to switch the font from Dank Mono to Recursive (`Rec Mono Duotone`). This commit is part of a switch from Dank Mono to Recursive. Although Dank Mono does render in VSCode, it is not correctly monospaced and therefore stopped working in some applications that have more strict font requirements, like the terminal emulator kitty (kitty >=0.36). https://www.recursive.design/ https://github.com/arrowtype/recursive https://sw.kovidgoyal.net/kitty/changelog/ https://sw.kovidgoyal.net/kitty/faq/#kitty-is-not-able-to-use-my-favorite-font Explanation from Dank Mono creator Phil Pluckthun via email: > Some terminal applications require a specific monospace flag to be set > in the font file that was only gaining traction after the font was > released. Some also just don't support fonts with ligatures. In Dank > Mono's case the specific flag that some applications require to select > the font as a monospaced one simply isn't set, and a different, older > one is set instead. Related issues: eigilnikolajsen/commit-mono#15 IdreesInc/Monocraft#26 IdreesInc/Monocraft#77 tonsky/FiraCode#1325 vercel/geist-font#33
br3ndonland
added a commit
to br3ndonland/dotfiles
that referenced
this issue
Oct 13, 2024
This commit will update the README to document the switch from Dank Mono to the Recursive font (`Rec Mono Duotone`). Although Dank Mono does render in VSCode, it is not correctly monospaced and therefore stopped working in some applications that have more strict font requirements, like the terminal emulator kitty (kitty >=0.36). https://www.recursive.design/ https://github.com/arrowtype/recursive https://sw.kovidgoyal.net/kitty/changelog/ https://sw.kovidgoyal.net/kitty/faq/#kitty-is-not-able-to-use-my-favorite-font Explanation from Dank Mono creator Phil Pluckthun via email: > Some terminal applications require a specific monospace flag to be set > in the font file that was only gaining traction after the font was > released. Some also just don't support fonts with ligatures. In Dank > Mono's case the specific flag that some applications require to select > the font as a monospaced one simply isn't set, and a different, older > one is set instead. Related issues: eigilnikolajsen/commit-mono#15 IdreesInc/Monocraft#26 IdreesInc/Monocraft#77 tonsky/FiraCode#1325 vercel/geist-font#33
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In macOS Font Book, there's a smart collection for Monospaced (Fixed Width) fonts.
I've tried to look into how this is determined, and I'm not sure. FontForge docs seems to say that it (FF) should decide for itself when the font is monospaced, although it also mentions some (OS/2?) setting for this, and I don't know if this would have an impact.
tl;dr it would be nice if Monocraft was automatically added to the Fixed Width smart collection in Font Book, and I'm not sure why it doesn't show up there.
The text was updated successfully, but these errors were encountered: