blade support : primary mode lost though ?

[jcelle]

Hi there,
Thanks for having added Blade support in beta 2, that's awesome.
I immediately turned it on for HTML and PHP modes.
Blade tags are now properly spotted and colored.

I noted two defects though:

- Unless I forgot something primary mode seems however lost (non embedded code).
- Tags within strings are not handled but this could be due to previous one.

I am attaching a screenshot of a php file opened in HTML mode.
All the best.

[Clark]

Hmm...Not sure what's going wrong. Try a default config.  vs +new -sc <new-config-dir>.

[jcelle]

Indeed this works with a blank new configuration.
I have tried to import my usual settings and clearly noticed the loss of proper coloring during the import process (as se window is dynamically updated during import process).
I tried all over again and now I am back with 2 configuration directories: what files should I inspect to track the culprit setting ?

[Clark]

I suspect you made changes to your color coding profile. Did you add new color coding items for processing braces (possibly to add blade support)?

[jcelle]

silly me I had registered a 'blade' language trying to do this (configuring but never managed to get it work and then forgot it..).
Removing it from working configuration, exporting again and applying import on fresh config worked: I'll keep this config from now on.

Many thanks for your help Clark.

[jcelle]

Hi again,
Note that then @endforeach is not completely colored, I guess engine stops coloring after @endfor ('each' is not colored as Blade keyword).

[Clark]

Fixed for beta 3

[jcelle]

cool! don't forget @foreach

[Clark]

I should have mentioned what was fixed.  The issue with @<keywords> being only partially color coding is fixed for beta 3.

Thanks for posting