Input's method seems to be fundamentally very different to this. Monaspace keeps the grid intact and only changes the characters visually (situationally overlaps wide letters to neighbouring narrow characters' spaces). Input just pretends to be monospace in its aesthetics, I don't really understand what's supposed to be special with that.
replyFair points on the technical implementation.
replyI more meant the idea of using different fonts in the same buffer to represent different kinds of text.
Input is a proportional font.
replyMonaspace is a monospace font that uses contextual alternatives: it changes how letters look depending on surrounding letters.
They are nothing alike in their approach to this problem.
(Also this is a marketing piece. Contextual alternatives is not a new tech.)
> Input is a proportional font.
replyit is also a monospaced font
Yes there is a version of Input that is a monospaced font and doesn't solve the problem tackled by Monaspace and the proportional version of Input and is therefore as relevant to this discussion as .. I dunno .. Courier New.
replyHonest question: does emacs (GUI) not support this?
replyEmacs totally supports this!
replyMixing monosoace and proportional fonts can be a little strange, but there are some 3rd party packages or guides (prot has one iirc) to workaround it.
Which editors?
replyGiven GitHub is owned by Microsoft, I think VS Code supporting mixing fonts in a buffer would be a good start!
replyYes, I configured VS Code to use Monaspace a while ago.
reply