Sublime Forum

Build 3114 breaks Laravel Blade plugin syntax

#1

Hey, after upgrading to Build 3114, my files using Laravel Blade syntax (from this plugin - https://github.com/Medalink/laravel-blade) now display broken syntax.

For example, in this snippet, the highlighter does not properly identify the ending ) parenthesis in the @if structure. As a result, all following content is interpreted as code instead of markup:

subl_break_laravel.png742×267 21.1 KB

The highlighter seems to function if I add an extra ) after the already existing ), but this would clearly produce syntactically incorrect code.

This is how the same plugin highlights in Build 3103: http://i.imgur.com/p8QgaBN.png

I’m thinking something relatively significant has changed in the syntax engine which would lead to this compatibility issue.
Anyone else having syntax issues with similar plugins?

Platform details: Gentoo Linux x86_64 kernel 4.4.2

0 Likes
#3

Thanks a lot! :smiley:

Unfortunately, the new build still has a few other problems (most importantly it exhibits sloppy performance for me) so I still can’t fully update at the moment. :frowning:

0 Likes
#4

@Kirov care to elaborate? Although there appear to be a number of syntax related bugs with this build, performance is improved across the board for me.

0 Likes
#5

Well, I’m experiencing a lot of stuttering on scrolling and general feel of UI latency. This is always reproducible and switching to 3103 always removes the issue.

Possibly related to this is the high CPU usage that I’m getting out of nowhere, upwards of 25% on 6 out of 8 cores. I’ve noticed this because the CPU fan geared up all of a sudden, which very rarely ever happened for me while in Sublime Text (mostly when doing large volume file searches or opening huge files).

I’d be willing to provide some info for debugging if I’d knew what.

Also worth mentioning - generally I have about 40-50 files open across 4 views, most over 200 lines long and with different syntaxes.

0 Likes
#6

Which platform are you running on?

0 Likes
#7

Linux 4.4.2-gentoo #3 SMP PREEMPT Wed Apr 6 02:19:26 EEST 2016 x86_64 Intel® Core™ i7-6700K CPU @ 4.00GHz GenuineIntel GNU/Linux

0 Likes
#8

Thanks, and which graphics card / driver?

0 Likes
#9

Nvidia GeForce GTX 980 Ti on official Nvidia driver version 361.28.

I see there are new kernel and video driver versions. I’ll try to update both and see if this still happens.

0 Likes
#10

It may be that some of the rendering refinements have had an adverse effect in Linux especially with some Nvidia chipset & driver combos.

Assuming you don’t find a result playing with kernel / driver versions, perhaps you could try some of the recent dev builds as a portable install and see if you can find which version introduced a noticeable problem since 3103. That would probably help to identify the problem if one exists.

2 Likes
#11

High CPU usage usually indicates the indexer is going through your project. By default it uses one process per core. In some large projects this can spin up your fan until complete. You can change the number of index workers to reduce the load.

If one of the workers is running on the same core as the UI thread, it may cause some stuttering. Since many of the syntaxes changes since the last build, it has likely caused a reindex of the project. Once complete you should be in better shape.

2 Likes
#12

Ok guys, I’ll follow both suggestions and post my findings here.

0 Likes