You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
Uh oh!
There was an error while loading. Please reload this page.
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: