You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not aware of any explicit changes we do with fonts or ligatures, but it might be that the code highlighting plays a role here. Does the bug occur in Dafny source only or VSCode wide?
It seems that the VSCode team is currently working on language specific ligatures in microsoft/vscode#10435 (comment), which will probably be shipped with the next release.
I'd suggest we wait until these changes are released, if the problem persists we can take another look at it 🙂
Does the bug occur in Dafny source only or VSCode wide?
Only occurs in .dfy files, and only when this extension is enabled, so definitely appears to be somehow related to this.
It seems that the VSCode team is currently working on language specific ligatures in microsoft/vscode#10435 (comment), which will probably be shipped with the next release.
Using MS's cascadia code font with ligatures enabled, this extension being enabled appears to influence how the ligatures render in
.dfy
files.e.g. extension disabled
vs extension enabled
This is on MacOS Catalina 10.15
VS Code 1.39.2
Extension 0.17.1
Cascadia Code 1910.04
(latest versions of everything)
The text was updated successfully, but these errors were encountered: