Thank you for the amazing ST4 package. It is super useful. I encountered issues with the default definition for Objective-C files:
{
"syntax": "Objective-C/Objective-C",
"match": "all",
"rules": [
{"globmatch": "**/*.m"},
{"contains": "^\\s*(@(interface|class|protocol|property|end|synchronised|selector|implementation)\\b|#import\\s+.+\\.h[\">])"}
]
},
where I had to change the rule contains to:
{"contains": "\\s*(@(interface|class|protocol|property|end|synchronised|selector|implementation)\\b|#import\\s+.+\\.h[\">])"}
There, I removed ^ and it then worked. Do you know a simple explanation why ^ is not accepted? I checked with my .m files and the rule including ^ results in positive matches when using regex search functionality of ST4 editor. So, the problem should not be with my .m files.
Thank you for the amazing ST4 package. It is super useful. I encountered issues with the default definition for Objective-C files:
{ "syntax": "Objective-C/Objective-C", "match": "all", "rules": [ {"globmatch": "**/*.m"}, {"contains": "^\\s*(@(interface|class|protocol|property|end|synchronised|selector|implementation)\\b|#import\\s+.+\\.h[\">])"} ] },where I had to change the rule
containsto:{"contains": "\\s*(@(interface|class|protocol|property|end|synchronised|selector|implementation)\\b|#import\\s+.+\\.h[\">])"}There, I removed
^and it then worked. Do you know a simple explanation why^is not accepted? I checked with my.mfiles and the rule including^results in positive matches when using regex search functionality of ST4 editor. So, the problem should not be with my.mfiles.