CODEWITHSUNDEEP
swiftsublimetext2syntax-highlightingtextmatetextkit
OscarVGG
OscarVGG

Reputation: 2670

.tmlanguage escape sequences and rule priorities

I'm implementing a syntax highlighter in Apple's Swift language by parsing .tmlanguage files and applying styles to a NSMutableAttributtedString.

I'm testing with javascript code, a javascript.tmlanguage file, and the monokai.tmtheme theme (both last included in sublime text 3) to check that the syntax get highlighted correctly. By applying each rule (patterns) in the .tmlanguage file in the same order they come, the syntax is almost perfectly highlighted.

The problem I'm having right now is that I don't know how to know that a quote (") should be escaped when it has a backslash before it (\"). Am I missing something in the .tmlanguage file that specifies that?. Other problem is that I have no idea how to know that other rules should be ignored when inside others, for example:

I'm getting double slashes taken as comments when inside strings: "http://stackoverflow.com/" a url is recognised as comment after //

Also double or single quotes are taken as strings when inside comments: // press "Enter" to continue, the word "Enter" gets highlighted as string when should be same color as comments

So, I don't know if there is some priority for some rules over others in the convention, or if there is something in the files that I haven't noticed.

Help please!

Update:

Here is a better example of what I meant by escape quotes:

I'm getting this: enter image description here while all the letters should be yellow except for the escaped sequence (/") which should be blue.

The question is. How do I know that /" should be escaped? The rule for that piece of code is:

enter image description here

Upvotes: 0

Views: 1746

Answers (3)

CodeManX
CodeManX

Reputation: 11865

Assuming that / is the correct character for escaping a double quote mark, the following should work:

    "str_double_quote": {
        "begin": "\"",
        "end": "\"",
        "name": "string.quoted.double.swift",
        "patterns": [
            {
                "name": "constant.character.escape.swift",
                "match": "/[\"/]"
            }
        ]
    }

You can match an escaped double quote mark (/") and a literal forward slash (//) in the patterns to consume them before the end marker is used to handle them.

If the character for escaping is actually a backslash, then the tricky bit is that there are two levels of escaping, for the JSON encoding as well as the regular expression syntax. To match \", the regular expression requires you to escape the backslash (\\"). JSON requires you to escape backslashes and double quotes, resulting in \\\\\" in a TextMate JSON grammar file. The match expression would thus be \\\\[\"\\\\].

Upvotes: 0

attempt0
attempt0

Reputation: 834

Maybe I am late to answer this. You can apply the following method.

  1. (Ugly) In your end regex, use ([^/])(") and in your endCaptures, it would be

    1 = string.quote.double.js
    2 = punctuation.definition.string.end.js

  2. If the string must be single line, you can use match=(")(.*)("), captures=

    1 = punctuation.definition.string.begin.js
    2 = string.quote.double.js
    3 = punctuation.definition.string.end.js
    and use your patterns

  3. You can try applyEndPatternLast and see if it is allowed. Set applyEndPatternLast=1 will do.

Upvotes: 1

MattDMo
MattDMo

Reputation: 102852

The priority is that earlier rules in the file are prioritized over later rules. As an example, in my Python Improved language definition, I have a scope that contains a series of all-caps constants used in Django, a popular Python web framework. I also have a generic constant.other.allcaps.python scope that recognizes (just about) anything in all caps. Since the Django constants rule is before the allcaps rule in the .tmLanguage file, I can color it with a theme using one color, while the later-occurring "highlight everything in all caps" only grabs identifiers that are NOT part of the first list.

Because of this, you should put your "comments" scope(s) as early in the file as possible, then write your parser in such a way that it obeys the rule I described above. However, it's slightly more complicated than that, as I believe items in the repository are prioritized based on where their include line is, not where the repository rule is defined in the file. You may want to do some testing to verify that, though.

Unfortunately I'm not sure what you mean about the escaped quotes - could you expand on that, and maybe add an example or two?

Hope this helps.

Upvotes: 0

Related Questions