[solved] New Syntax - highlighting function in conflict with keywords

[Perro-Del-Ingles]

i made this with how little i understood

main:
    #- include: pawn_string
    #- include: pawn_character
    #- include: pawn_coment
    - include: pawn_function
    #- include: pawn_numbers
    - include: pawn_keywords
#
pawn_function: # function definition... start with public or stock
#
    # "\s" no work for newline, any idea?
    - match: '(public|stock)[\s]*([A-Za-z_][\w_]*)[\s]*(\()' 
      captures:
        2: entity.name.function.definition.c
        3: punctuation.definition.group.start
      push:
        - match: \)
          scope: punctuation.definition.group.end
          pop: true
#
 pawn_keywords:
    - match: \s*\b(Float|new|enum|public|forward|native|char|const|static|stock)\b
      scope: storage.type.c

but conflicts with pawn_keywords and not set storage.type.c to public/stock

[kingkeith]

Add hightlighting rule for ~ character

one way of visualizing it is: the view has a sublime-syntax (or tmLanguage) file assigned to it inside the sublime-syntax file, there can be many contexts a context might define the rules for matching attributes inside a html tag for example, which could also state that it needs to be followed by a different context such as an end of tag character contexts are held on a stack, such that only the context at the top of the stack is active at once (although any meta_scopes from the other context…

tl;dr:

• regular expressions can only match one line at a time in syntax definitions
• characters are consumed so that if one expression matches public or stock, the other can’t unless it uses a lookbehind (not recommended)

[Perro-Del-Ingles]

thanks for the info