![]() ![]() ![]() First way is to make some wildcard for whitespaces for example ((SPC)) so it can be used like this: ((SPC))* as "Open" and ((EOD)) as "Close" in "Comment style".I think of 3 ways to do that (and all needs new feature). Maybe I misunderstood something and it can be done in some simple way, but I cannot figure it out. I tried * as "Open" in "Comment style" with success (partial, because semicolon is also colorized as comment) in line 5, but for line 6 ' *' won’t work properly. I selected "Allow preceding whitespace" in "Line comment position", so first 4 lines are formatted properly as comments. My problem is that I cannot figure how to make comments colorized in all above cases and not in multiplication. VAR4 = VAR5 * VAR6 * comments after semicolon and space VAR1 = VAR2 * VAR3 * comments can start after semicolon * This is also comment (with preceding whitespace) If you still need to use "F" as a folding in code type, try to use Folding in code 2. So, you can't have ambiguous characters/strings in both numbers and Folding in code 1 types. Think of your example rewritten in C-like syntax, and it will be more obvious what I am talking about.: So, 16#F will trigger number recognition, but number algorithm will first check for number boundaries before checking for number content, thus "F" will be treated as Folding in code 1 rather than as a number. Well, numbers end when first whitespace is found, or first forward keyword type, and Folding in code 1 IS a forward keyword type. It was primarily created for stuff similar to C curly brace folding points: You see Folding in code 1 style always matches searched string, regardless of surrounding characters. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |