-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lua inequality ~= rendered counter-intuitive #1171
Comments
According to changelog, it was removed in v 3.0 #381. Maybe you need to update? |
I'll check, thanks! |
I'm confused - Windows Fonts applet does show that there is no such ligature in the selected font set. But vscode still insists on older rendering. Looks like vscode specific issues (or taking into account that Windows Terminal experiences the same problems - gdi+ specific issue. Will check how it will persist after restart?.. |
Yup, vscode ligatures have been fixed with restart (though Windows Terminal have not). You could close this issue though. Much thanks! |
We also have this note about cleaning up fonts on Windows. Might not be relevant, but it’s something you can try: |
Lua uses
~=
for inequality, and it looks counter-intuitive if ligatures enabled. I don't see any language where it would be meaning approximately equal, so it makes no much sense (IMVHO) to render it this way, and we would rather see something very similar to how!=
is rendered.The text was updated successfully, but these errors were encountered: