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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

color scheme is modified twice #66

Open
dungsaga opened this issue Nov 13, 2017 · 0 comments · May be fixed by #50
Open

color scheme is modified twice #66

dungsaga opened this issue Nov 13, 2017 · 0 comments · May be fixed by #50

Comments

@dungsaga
Copy link

dungsaga commented 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.

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 dungsaga linked a pull request Nov 13, 2017 that will close this issue
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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant