<![CDATA[using "FOR" in language definition causes unexpected results]]>We use a language definition file for our scripting software in Notepad++
We have an open/close folding definition that includes FOR and END_FOR (in addition to other standard commands)
The syntax highlighting highlights FOR, but also highlights the letters “for” and “FOR” in words that contain those strings (not just when they exist alone. So if we use FORCE, FOREIGN, FORMAT, REINFORCMENT, BEFORE or other words used as a variable name (not part of our language definition file), the “FOR” part is still highlighted. Since the text editor thinks you are calling the function FOR it messes up code collapsing and is quite a nuisance. Is there a way to fix this. It doesn’t seem to be an issue for other commands like IF, AND, OR… why for FOR?

]]>https://community.notepad-plus-plus.org/topic/14672/using-for-in-language-definition-causes-unexpected-resultsRSS for NodeTue, 06 Oct 2026 03:13:19 GMTMon, 23 Oct 2017 17:12:17 GMT60<![CDATA[Reply to using "FOR" in language definition causes unexpected results on Mon, 23 Oct 2017 22:43:44 GMT]]>bingo…thankyou thankyou thankyou!

]]>https://community.notepad-plus-plus.org/post/27561https://community.notepad-plus-plus.org/post/27561Mon, 23 Oct 2017 22:43:44 GMT<![CDATA[Reply to using "FOR" in language definition causes unexpected results on Mon, 23 Oct 2017 19:13:22 GMT]]>@Charlie-Fuller

I’m guessing your FOR, END_FOR definitions are in the Folding in code 1 style box. Try moving them to the Folding in code 2 style (separators needed) box.

]]>https://community.notepad-plus-plus.org/post/27557https://community.notepad-plus-plus.org/post/27557Mon, 23 Oct 2017 19:13:22 GMT