Incompatible with ST3 Build 3103

[dschu-lab]

Hey there,

could you please update the packages.json to make this work with build 3103 again?

Thanks!

[andrewcaulfield]

Confirming that also have an issue with latest Sublime build 3103.

Cheers.

[GC-Mark]

+1

[djekl]

Also having issues, seems to work if you uninstall then reinstall. But once you close and re-open Sublime it breaks again...

[GC-Mark]

I just reinstalled, and it works. It also works after a sublime restart, so not sure why it doesn't for you @djekl

[djekl]

@GC-Mark Open a new window, then a project. It wont work then. I will see if I can get an example made up

[GC-Mark]

@djekl just tried that, still works 😕

[djekl]

I only get 30 seconds on cloudy, so before I took the video I removed the package, and then installed it again. Closed all Sublime and it works as before. Then the video was started and you will see the issue cc:// @GC-Mark

[GC-Mark]

Don't know if it makes a difference, but im using a different project switcher - https://github.com/randy3k/Project-Manager

P.S. What theme are you using, it looks awesome!

[rginnow]

+1 Broke when I upgraded my Sublime version to this new build.
Uninstalled and reinstalled, and it worked. Quit, reopened, and it still worked.
Even did a new window in a different Laravel project and it worked there too.

Not sure why, but I think it's a small issue to be looked into.

[djekl]

@GC-Mark The theme I am using is called Material Theme. It has some bugs with regards to padding, but they are explained in the readme.

Here is my sublime settings file - https://gist.github.com/djekl/8eca76509c7d7915cc14

[Medalink]

Looks like they did not roll these out to the dev channel so I missed this before release. For now, use the dev release of 3102 as a workaround until I can get this fixed.

[stulogy]

I had this issue too, and rolled back to 3102 as suggested. I'm now getting this weird issue whereby if you put @if () statements inside attributes, then it breaks the rest of the display. See my screenshot.

It didn't used to do this, it would just highlight everything in the attribute as yellow.

[cjaoude]

Reinstalling the package helped. Can't say yet whether issues will crop back up.

[casenjo]

Tried removing and reinstalling the package but it didn't fix it. Downgraded to 3102 for now, will wait :)

[Skintillion]

Uninstall
Close Sublime
Open Sublime
Reinstall
Close Sublime
Open Sublime.

That worked ok for me.

[razikallayi]

Incompatible with ST3 Build 3103

+1

[Skintillion]

It works great.

[marwan2]

The same issue also with me

[hollanbo]

same problem.

[harhoo]

Works fine for me; initially it didn't, so Iuninstalled and reinstalled with no success before realising that ST had lost all its syntax associations. So View > Syntax > Open all with current extension as and I was back in business.

[JPT62089]

Uninstall
Close Sublime
Open Sublime
Reinstall
Close Sublime
Open Sublime.

That worked ok for me.

This worked for me, too! Thanks, @Skintillion!

[ben-sharp]

Following @Skintillion instructions I am able to see my mark up nicely, however the javascript in the section at the bottom of my template now has zero highlighting whatsoever, not sure if this was always the case.

[stulogy]

Basic highlighting is working for me now. However when using conditionals it breaks the rest of the highlighting. See my screenshot. This was working before.

On Feb 10, 2016, at 5:47 PM, Benjamin Sharp [email protected] wrote:

Following @Skintillion instructions I am able to see my mark up nicely, however the javascript in the section at the bottom of my template now has zero highlighting whatsoever, not sure if this was always the case.

—
Reply to this email directly or view it on GitHub.

[nuhh]

As @stulogy said, I have same problem

[JayBizzle]

@ryanmortier it doesn't work when your conditional starts within a HTML element

<div class="@if($something) active @endif">

[ryanmortier]

Oops, sorry I didn't see your comment before I deleted mine or I wouldn't have deleted my comment. Yes you're correct, using it inside an HTML attribute breaks for me too.

[cklmercer]

It works for me within an HTML element, but does not work for me within the quoted part of an attribute.

Works

<div class="col-md-8 text-content" @if($error) class="error" @endif>

Does Not Work

<div class="@if($error) error @endif">

[stulogy]

Agreed.

I think it’s the @ symbols that are throwing off the highlighter. Before this was never a problem, possibly because it ignored @ symbols.

On Feb 11, 2016, at 3:13 PM, Cody Mercer [email protected] wrote:

It works for me within an HTML element, but does not work for me within the quoted part of an attribute.

Works

Does Not Work

— Reply to this email directly or view it on GitHub.

[JayBizzle]

I just created a pull request that hacks a fix for this issue. See #92

[RicardoEmpre]

For me it has problems with the vuejs line
@click="selectResource(resource)".
If you remove the @ or the parenthesis in that line, it works OK.

Also if you use v-on:click instead of @click it works ok.

[estebanprimost]

@Skintillion 👍 Thanks.

[jago86]

Have the same issue @stulogy, @if breaks the rest of display

[matthewnance]

Just confirming - Dev build 3107 has not solved the issue even after a fresh install. Strange how inconsistent this seems to be, none of the aforementioned fixes have solved the issue on my end.

[JTallis]

I had this issue and I did what some others have done which is reinstalling the package and it seems to work so far for me.