somethings up with my highlighting...

[Mike James]

I've got:

babel sublime installed, v8.6.3
oceanic-next-color-scheme installed v0.1.11
sublime 3 latest (3103)

user settings:

{
    "color_scheme": "Packages/User/SublimeLinter/Oceanic Next (SL).tmTheme",
    "font_face": "Hack",
    "font_size": 14,
    "ignored_packages":
    [
        "Vintage"
    ],
    "tab_size": 2,
    "theme": "Oceanic Next.sublime-theme",
    "translate_tabs_to_spaces": true
}

and it looks like this :(

any ideas?

[Dmytro Voronianski]

@export-mike that's crazy.. never encountered smth like this. Are you on Mac? Maybe you have additional packages that can conflict with babel-sublime?

[Mike James]

possibly... here's my list.. is there a way to get a list of all packages and versions?

[Dmytro Voronianski]

@export-mike Package Control -> List Packages

[Dmytro Voronianski]

Maybe Numix?

[Mike James]

I reinstalled everything working fine now, thanks for your help

[Oleg Akbarov]

Got the same issue. Interestingly enough it appears in the same place — after destructuring:

<DoorHeader {...this.props} />

Reinstall doesn't help so far.

[Mike James]

Yeah I've since switched to atom. So far its a great experience

On Thu, 28 Apr 2016 16:53 Oleg Akbarov, [e-mail] wrote:

Got the same issue. Interestingly enough it appears in the same place —
after destructuring:

<DoorHeader {...this.props} />

Reinstall doesn't help so far.

—
You are receiving this because you modified the open/close state.

Reply to this email directly or view it on GitHub
#40 (comment)

[Oleg Akbarov]

@export-mike you got this issue again after reinstall? 😭

[Mike James]

Yeah my bad, I thought everything was OK but turns out it wasn't, sorry I never updated the issue

[Oleg Akbarov]

I'd be grateful for any ideas on this. Atom way too slow for me.

[Mike James]

When was the last time you tried it? I've been using the nuclide plugins
and babel plugins with has millions of downloads. I did find it to be slow
on an old macbook pro 2009

On Thu, 28 Apr 2016 17:02 Oleg Akbarov, [e-mail] wrote:

I'd be grateful for any ideas on this. Atom way too slow for me.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#40 (comment)

[Oleg Akbarov]

@export-mike Last summer i belive, quite a while ago.

By the way seems like this is a Babel-Sublime issue

[Oleg Akbarov]

@export-mike This helped me:

In sublime:
Syntax -> Open all with current extension as... -> Babel -> JavaScript (Babel)

[Dmytro Voronianski]

@olegakbarov good point, probably this should be added to README.

[Oleg Akbarov]

@voronianski PR? 😉

[Jim]

@olegakbarov Thanks man. You save my day.