Closed Auroriax closed 1 year ago
Not 100% sure, but my hunch is that it might have something to do with how the >
character is escaped in the puzzlescript source code that can confuse the parser. I should probably replace the >
with another glyph that's escape-safe, like a special instruction such as copy:
.
So it seems that PS syntax highlighting is prone to break on projects that have a very large source code (e.g. Gridblocked), it seems most people with gargantuan PS source code (e.g. Selene's Garden) don't use the editor to edit code because it's prone to breaking. So it could be a CodeMirror issue. Might be worth it to bring this up with increpare?
As for the editor crashing, seems it could've been a stuck for loop or a memory overflow... I don't have enough info to go on to fix it.
This has become a messy issue. To summarize:
Reported to increpare as https://github.com/increpare/PuzzleScript/issues/947. Closing here.
It seems that if you scroll too quickly the syntax highlighting can get weird & can cause ctrl+clicking a level to crash in some cases:
Could it break because I changed the syntax highlighing code?