-
Notifications
You must be signed in to change notification settings - Fork 25
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
color scheme is modified twice #66
Comments
dungsaga
pushed a commit
to dungsaga/Sublime-Colorcoder
that referenced
this issue
Nov 13, 2017
When color scheme is modified by another package (such as SublimeLinter), Colorcoder should not modify it again. Right now, it add its scopes and appends "(Colorcoded)" to color scheme name.
dungsaga
added a commit
to dungsaga/Sublime-Colorcoder
that referenced
this issue
Nov 13, 2017
When color scheme is modified by another package (such as SublimeLinter), Colorcoder should not modify it again. Currently, Colorcoder added its scopes and appends "(Colorcoded)" to color scheme name.
dungsaga
added a commit
to dungsaga/Sublime-Colorcoder
that referenced
this issue
Nov 13, 2017
When color scheme is modified by another package (such as SublimeLinter), Colorcoder should not modify it again. Currently, Colorcoder added its scopes and appends "(Colorcoded)" to color scheme name twice.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When color scheme is modified by another package (such as SublimeLinter), Colorcoder should not modify it again.
Currently, Colorcoder added its scopes and appends "(Colorcoded)" to color scheme name twice.
The text was updated successfully, but these errors were encountered: