Haxe (*.hx) file highlight becomes broken starting from the place where conditional occurs ![broken](https://cloud.githubusercontent.com/assets/674995/13553226/9733cb96-e38a-11e...) Btw it works if one adds a negation to the condition: ![normal](https://cloud.githubusercontent.com/assets/674995/13553225/972f039a-e38a-11e...) Actually it's quite an old bug. I think it was there always.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/936
Seems to be a Scintilla bug. Can you report it there also?
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/936#issuecomment-192851224
Not sure it's Scintilla itself, looks like some part are "just" not styled. Maybe Haxe uses a trick for commented-out preprocessor like C can (disabled by default though), and uses different styles there.
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/936#issuecomment-192899934
Yes, Haxe uses similar to C preprocessor, with similar syntax. So should I create a bug report at scintilla sourceforge or not?
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/936#issuecomment-192989539
I tried SciTE - it doesn't have haxe support. FlashDevelop uses scintilla too and I don't think it has any conditionals syntax highlight issues though it's the most popular IDE among Haxe developers. So are you sure it's a scintilla bug?
--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/936#issuecomment-195307591
Closed #936 via bbdf56fc2e2c978de6a61c3be56dfeb5bc6963ef.
So are you sure it's a scintilla bug?
Actually it's not, it's "just" that we don't set the "inactive preprocessor" styles, and anyway Haxe's preprocessor directives are different from C, and we forget to disable preprocessor tracking for Haxe. Done now.
github-comments@lists.geany.org