Hello all -
My company just bought three licenses, we’re in the process of converting the entire dev team over. Love it!
I’m trying to get a few extra things working for color-coding PHP, some of which are specific to our company (our language translation indexes, for example) and some things that aren’t colored the way we’d like (variables inside double-quoted strings).
It seemed logical to create a new tmLanguage file that would import the existing source.php - but I’m having some troubles here. If I do not import the PHP syntax, my definitions work. However, upon importing them, my defs stop working - they don’t even show up when I do the ctrl+shift+alt+p thing. Another issue is that some plugins, notably phpcs, use the syntax of the current file to determine if the view is PHP or not.
I can post my code tomorrow for people to look at if anyone is interested. In the meantime, is there a better way to add just one or two rules? A co-worker made a plugin to add a scope to regions, and it sorta worked, but it applies all the styles as background, even if the colors are specified with foreground as the key. This happens even if we re-use an existing color definition. Very strange, and doesn’t seem like it should behave that way.
Thanks for reading
MPEDrummer