Author Topic: blade support : primary mode lost though ?  (Read 712 times)

jcelle

  • Senior Community Member
  • Posts: 189
  • Hero Points: 5
blade support : primary mode lost though ?
« on: August 06, 2020, 08:17:30 am »
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

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6273
  • Hero Points: 484
Re: blade support : primary mode lost though ?
« Reply #1 on: August 06, 2020, 11:52:17 am »
Hmm...Not sure what's going wrong. Try a default config.  vs +new -sc <new-config-dir>.

jcelle

  • Senior Community Member
  • Posts: 189
  • Hero Points: 5
Re: blade support : primary mode lost though ?
« Reply #2 on: August 06, 2020, 01:27:43 pm »
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

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6273
  • Hero Points: 484
Re: blade support : primary mode lost though ?
« Reply #3 on: August 06, 2020, 01:31:16 pm »
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

  • Senior Community Member
  • Posts: 189
  • Hero Points: 5
Re: blade support : primary mode lost though ?
« Reply #4 on: August 06, 2020, 01:57:29 pm »
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

  • Senior Community Member
  • Posts: 189
  • Hero Points: 5
Re: blade support : primary mode lost though ?
« Reply #5 on: August 06, 2020, 02:24:45 pm »
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

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6273
  • Hero Points: 484
Re: blade support : primary mode lost though ?
« Reply #6 on: August 06, 2020, 02:57:23 pm »
Fixed for beta 3

jcelle

  • Senior Community Member
  • Posts: 189
  • Hero Points: 5
Re: blade support : primary mode lost though ?
« Reply #7 on: August 06, 2020, 10:31:18 pm »
cool! don't forget @foreach

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6273
  • Hero Points: 484
Re: blade support : primary mode lost though ?
« Reply #8 on: August 06, 2020, 11:18:52 pm »
I should have mentioned what was fixed.  The issue with @<keywords> being only partially color coding is fixed for beta 3.

Thanks for posting