Summary
The Place of Interest Sign / Cmd symbol ⌘ (U+2318) renders with very narrow / zero right sidebearing, so it visually collides with the immediately-following character (no inter-glyph gap). This is most noticeable in keyboard-shortcut notation like ⌘O, ⌘D, ⌘F, where the letter appears glued to the symbol.
Reproduction
In any monospace context using Hack — e.g. terminals, code editors, notebooks — render text like:
⌘O Quick Switcher
⌘D Toggle
⌘F Global Search
The O, D, F sit flush against the right edge of the ⌘ glyph, unlike other adjacent character pairs (e.g. AO, MD), which have the expected monospace spacing.
Expected
⌘ should have sidebearings consistent with other glyphs in its advance width, so adjacent characters render with the normal monospace gap.
Actual
⌘ visually touches the next character with no spacing, looking like a single mashed glyph at common sizes.
Workaround
Switching to a different monospace font (e.g. Menlo, SF Mono, JetBrains Mono) renders ⌘O etc. with proper spacing, confirming the issue is glyph-metric rather than app-side.
Environment
- App: Reproduced in the Warp terminal (macOS), font set to Hack. Other apps using Hack at the same size are expected to show the same; happy to verify if helpful.
- OS: macOS (Apple Silicon)
- Font: Hack (regular weight; happy to add the exact version on request)
Notes
This is small but very visible for users who write a lot of macOS shortcut notation in their notes / READMEs / terminal output. A screenshot can be attached if useful.
Summary
The Place of Interest Sign / Cmd symbol ⌘ (U+2318) renders with very narrow / zero right sidebearing, so it visually collides with the immediately-following character (no inter-glyph gap). This is most noticeable in keyboard-shortcut notation like
⌘O,⌘D,⌘F, where the letter appears glued to the symbol.Reproduction
In any monospace context using Hack — e.g. terminals, code editors, notebooks — render text like:
The
O,D,Fsit flush against the right edge of the ⌘ glyph, unlike other adjacent character pairs (e.g.AO,MD), which have the expected monospace spacing.Expected
⌘ should have sidebearings consistent with other glyphs in its advance width, so adjacent characters render with the normal monospace gap.
Actual
⌘ visually touches the next character with no spacing, looking like a single mashed glyph at common sizes.
Workaround
Switching to a different monospace font (e.g. Menlo, SF Mono, JetBrains Mono) renders
⌘Oetc. with proper spacing, confirming the issue is glyph-metric rather than app-side.Environment
Notes
This is small but very visible for users who write a lot of macOS shortcut notation in their notes / READMEs / terminal output. A screenshot can be attached if useful.