Page 1 of 1
Quick tip for anyone using sublimetext
Posted: 21 Sep 2017, 02:18
by KuroiLight
Not sure if this should go in this section or another, but it pertains to writing AHK code using the available plugin in sublime_text.
Heres a quick fix a highlighting issue that occurs when writing in OneTrueBrace style with
if statements
the issue is with this line (78) in the tmLanguage file:
https://github.com/ahkscript/SublimeAut ... nguage#L78
just change the regex to
^\s*((?!\bif\b)\w+)(\()(.*)(\))\s*({)\s*(;?.*)$
This issue can still occur with other statements unless its expanded for those too. but it was most commonly annoying on if statements.
Re: Quick tip for anyone using sublimetext
Posted: 23 Sep 2017, 02:42
by BoBo
KuroiLight wrote:Not sure if this should go in this section or another, but it pertains to writing AHK code using the available plugin in sublime_text.
Heres a quick fix a highlighting issue that occurs when writing in OneTrueBrace style with
if statements
the issue is with this line (78) in the tmLanguage file:
https://github.com/ahkscript/SublimeAut ... nguage#L78
just change the regex to
^\s*((?!\bif\b)\w+)(\()(.*)(\))\s*({)\s*(;?.*)$
This issue can still occur with other statements unless its expanded for those too. but it was most commonly annoying on if statements.
Re: Quick tip for anyone using sublimetext
Posted: 11 Mar 2018, 12:06
by nnnik
It seems we missed this after adding the Editors section.
I moved it to the correct section now.
Re: Quick tip for anyone using sublimetext
Posted: 28 May 2018, 16:45
by Cerberus
KuroiLight wrote:Not sure if this should go in this section or another, but it pertains to writing AHK code using the available plugin in sublime_text.
Heres a quick fix a highlighting issue that occurs when writing in OneTrueBrace style with
if statements
the issue is with this line (78) in the tmLanguage file:
https://github.com/ahkscript/SublimeAut ... nguage#L78
just change the regex to
^\s*((?!\bif\b)\w+)(\()(.*)(\))\s*({)\s*(;?.*)$
This issue can still occur with other statements unless its expanded for those too. but it was most commonly annoying on if statements.
Hmm could you explain what this changes? I've edited my own version, so I don't really remember what it used to be and how that looked. My regex version is even shorter than the one on Github, even though I'm sure I installed the package after the latest Github version.
Re: Quick tip for anyone using sublimetext
Posted: 28 May 2018, 17:04
by swagfag
i think the original incorrectly considered the following a function definition:
Re: Quick tip for anyone using sublimetext
Posted: 28 May 2018, 17:43
by Cerberus
swagfag wrote:i think the original incorrectly considered the following a function definition:
Ahh, I see, yes, that's it! I probably never noticed because I always use spaces. I've added it to my .sublime-syntax file.