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
With Syntax Highlighter 0.4.4. I have the following colouration which I think is wrong:
When the extension is enabled: we can see that the string is no longer coloured with the string color: it makes it harder to read (which is not what the extension is trying to do :)):
Without the extension, this is correct:
The extension behave well for this kind of expression:
Another problem is with number (I'm using FiraCode, the != is displayed as unicode ≠ but it is only a ligature, should not be the problem here):
The first 0 is colored blue, the second is colored gray (or something like that) while I would expect them to use the same color..
I also have a crash after extended use (>30 minutes I think?) but as I played with the Enable/Disable, I no longer have the crash trace... And this is a separate problem anyway.
VSCodium information:
Version: 1.45.1 (user setup)
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-15T10:23:54.161Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
The text was updated successfully, but these errors were encountered:
Hello,
With Syntax Highlighter 0.4.4. I have the following colouration which I think is wrong:
When the extension is enabled: we can see that the string is no longer coloured with the string color: it makes it harder to read (which is not what the extension is trying to do :)):
Without the extension, this is correct:
The extension behave well for this kind of expression:
The quoted
'yes'
make it works.Another problem is with number (I'm using FiraCode, the
!=
is displayed as unicode ≠ but it is only a ligature, should not be the problem here):The first 0 is colored blue, the second is colored gray (or something like that) while I would expect them to use the same color..
I also have a crash after extended use (>30 minutes I think?) but as I played with the Enable/Disable, I no longer have the crash trace... And this is a separate problem anyway.
VSCodium information:
The text was updated successfully, but these errors were encountered: