Quotes unproperly highlit in Linux
Opened this issue · 14 comments
Describe the bug
Quotes are unproperly highlit for JS: opening a singlequote or a doublequote causes the rest of the line to be colored in quotes
To Reproduce
Steps to reproduce the behavior:
- Create a JavaScript (not sure if exclusive to JS) file
- Type (Minimal reproducible example, among others):
console.log('hello' + 54321);
console.log("hello" + 54321);
console.log(54321);
Expected behavior
The 54321 should have the same color everywhere, so should the parentheses
Desktop (please complete the following information):
- OS: Arch Linux
- Version v1.2.0
Just curious, are you running under Linux or Windows (or was it self-built)? It could be that the binary shipped for Linux includes a version of godot with a broken lineonly
Howdy. It was on Windows, gimmie a sec to just put my linux out of suspend and try it real quick. (Still convinced it's 100% a issue on your end though)
Ok! For future reference, my linux release has v4.2.1.stable.official.b09f793f5
as the godot engine version
Apologies for doubting you, it seems you were correct.
Linux version is indeed broken. #99 seems to speak about this but the author decided to leave no words. I'll link this issue there
Apologies for doubting you, it seems you were correct.
Linux version is indeed broken. #99 seems to speak about this but the author decided to leave no words. I'll link this issue there
It's all good! Sorry for bothering you further, but I'll try to dig it up a bit: what's the godot engine version for your windows build?
No idea, sorry :p
Perhaps rename issue to "Syntax highlighting broken on linux"?
(unless that's not the topic but that's what i'm reading at least)
Can confirm it only works improperly on Linux.
I'm wondering why that is...
griddycode/Scripts/settings.gd
Lines 66 to 69 in 6332a66
This is where the magic happens. To debug this I'd suggest logging the entry
, running GriddyCode, and entering a JavaScript file. Then compare the printed results on Linux and Windows.
I was able to reproduce the bug on Windows with rendering driver opengl3 - maybe that's the issue?
The only Windows PC I have is not performant enough to run it from DirectX, maybe someone who's downloaded it from the Releases folder could triple-check for DX as well?
i have this issue on windows too, not just linux
Weird; i don't have it