← Back to context

Comment by vermilingua

4 years ago

This is some schoolyard level stuff right here. The GP isn't using a monospaced font. Who, in the history of terminal emulators, has wanted to use a non-monospaced font in their terminal?

9 comments

vermilingua

Reply
onion2k  4 years ago

This is exactly the sort of "we can just skip that feature to make it faster!" edge case that I was talking about in my post.

  • vermilingua  4 years ago

    But it isn't an edge case! It's not an edge case, if it isn't a use case!

    This is an edge case as much as building a rasterizer directly into the terminal is an "edge case".

    • l30n4da5  4 years ago

      > But it isn't an edge case! It's not an edge case, if it isn't a use case!

      The fact that a random commenter on HN used a non-monospaced font with refterm actually makes it a use case.

      I do, however, agree that it is an edge case with a very low probability.

      2 replies →

  • 9935c101ab17a66  4 years ago

    Wait, what? Your edge case is something that no one would ever (should ever?) do? Are you going to complain about it not rendering scripts fonts correctly either?

    Also, it's worth noting that this isn't a compelling argument in the first place because the windows terminal doesn't even come close to rendering readable Arabic, it fucks up emoji rendering, etc – all cases that Casey was able to basically solve after two weekends of working on this.

    • onion2k  4 years ago

      In my 25 years of software development I've found that I'm rarely able to enumerate what an application should or shouldn't do on my own. Unless the app is extremely simple and has very few options it's incredibly unusual for any individual to understand everything about it. While I don't have a use case where I'd want to use a variable space font in a terminal, that doesn't mean such a case doesn't exist for anyone. Maybe some people want that feature.

      Windows Terminal, for some reason, gives users the option to change their font to one that isn't monospaced, so I'd argue that it should render them correctly if the user chooses to do that.