-
Notifications
You must be signed in to change notification settings - Fork 428
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syntax highlighting broken since build 3093 #167
Comments
@sampotts Yeah, it weirded me out as well. But from the looks of it, pre-3093 highlighting was actually incorrect and variables are supposed to be red. Might be a good idea to file an issue with base16-builder. Here is a quick bandaid to get things back the way they were. Add this to base16-ocean.dark.tmTheme: <dict>
<key>name</key>
<string>JS Variables</string>
<key>scope</key>
<string>source.js variable.other, variable.function.js</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#c0c5ce</string>
</dict>
</dict>
<dict>
<key>name</key>
<string>JS DOM Support</string>
<key>scope</key>
<string>support.type.object.dom</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#ebcb8b</string>
</dict>
</dict>
<dict>
<key>name</key>
<string>JS Properties</string>
<key>scope</key>
<string>constant.other.object.key.js, string.unquoted.label.js</string>
<key>settings</key>
<dict>
<key>foreground</key>
<string>#c0c5ce</string>
</dict>
</dict> |
Awesome. Only thing is, where do I find that file? I looked in Application Support, no dice? Edit. Found it. Had to change the |
@sampotts It's where your packages are installed and most likely in a folder named spacegray. On a Mac this will be ~/Library/Application Support/Sublime Text 3/Packages. |
I got this message from sublime text today:
However, I still have red everywhere. Is the "band aid" the only thing I can do right now? |
As title basically, upgraded to 3093 because the popup just wouldn't go away (needs a skip this version) and then it broke code highlighting in JS. I've tried 3094 and 3095, same deal. Looks like 3093 caused it.
Suggest sticking to 3092 if anyone was thinking of upgrading...
The text was updated successfully, but these errors were encountered: