Zulip Chat Archive

Stream: general

Topic: VS Code highlighting issue

Kevin Buzzard (May 27 2021 at 09:53):

Before I select the entire line:

#eval list.cons 4 list.nil -- [4]

After:
nospace.png

The space between the l's gets eaten.

Eric Rodriguez (May 27 2021 at 10:00):

image.png

looks fine to me - what font are you using?

Kevin Buzzard (May 27 2021 at 10:04):

Right -- it looks like that to me if I don't highlight it. Just l l is enough to make it happen. Maybe I have some weird VS Code setting on?

Eric Rodriguez (May 27 2021 at 10:17):

maybe, it's almost treating ll like a ligature because even the syntax highlighter seems to be getting confused

Eric Wieser (May 27 2021 at 10:52):

I think it's specifically l{U+2E31}l (l⸱l) that you end up with a weird ligature for

Eric Wieser (May 27 2021 at 10:53):

Or possibly l{U+00B7}l (l·l)

Eric Wieser (May 27 2021 at 10:53):

Aha, I get a ligature for that!

Eric Wieser (May 27 2021 at 10:54):

This is a bug in vscode itself - it shouldn't be allowing visible whitespace to form ligatures!

Anne Baanen (May 27 2021 at 10:56):

I blame the Catalans!

Eric Wieser (May 27 2021 at 11:05):

Does l· or ·l also have the ligature? edit: no, just l·l

Bryan Gin-ge Chen (May 27 2021 at 14:19):

I remember running into this last year, and I ended up adding a setting from this VS Code issue: https://github.com/microsoft/vscode/issues/106583

Add the following somewhere in your settings.json: "editor.fontLigatures": "'ccmp' off",.

Last updated: Dec 20 2023 at 11:08 UTC