Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

compatibility sublime 3.1.1 #164

Open
arnaudambro opened this issue May 18, 2018 · 5 comments
Open

compatibility sublime 3.1.1 #164

arnaudambro opened this issue May 18, 2018 · 5 comments

Comments

@arnaudambro
Copy link

Hi Wes, or anybody else,

Your theme is no compatible anymore with the new version of Sublime Text, would somebody be nice and smart enough to update it ? I miss it soooo much... 馃槱

Cheers
Arnaud

@rosston
Copy link
Contributor

rosston commented May 18, 2018

I'm using Sublime 3.1.1 build 3176 with Cobalt2 2.0.11 with no problems.

@arnaudambro, can you specify what version of Cobalt2 you're using? And can you maybe provide a screenshot and the relevant portion of your settings?

@arnaudambro
Copy link
Author

Sure ! Here it is below. You can see that React props are no longer italic, and the green color of objects key changed, so has the green color of the imported stuff.
screen shot 2018-05-18 at 15 34 51

@arnaudambro
Copy link
Author

On that one you can see that the arrow functions are not in orange if there is a semi-colon after the state
screen shot 2018-05-18 at 15 37 07

@aaeabdo
Copy link

aaeabdo commented Jun 8, 2018

@arnaudambro Wonder if you found a solution for this issue?

@rosston
Copy link
Contributor

rosston commented Jul 24, 2018

My strong hunch is that this was caused by updated syntax highlighting in Sublime 3.1 (build 3170). The release notes mention:

  • Many syntax highlighting improvements, including significant improvements to:
    • JavaScript, with thanks to Thomas Smith

For a temporary fix, you could try downgrading to Sublime Text 3.0 (build 3143) (by copying/editing the download links on the download page to refer to the desired build).

Longer term, I think this would require many patches to the cobalt2 syntax theme to fix. I don't use Sublime Text and am not really interested in fixing it myself, but here are some resources I found that could be useful for someone else to fix the issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants