Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document how Dank Mono is not actually monospaced
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
- Loading branch information