-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
Update color scheme word_separators, change LICENSE year #357
Conversation
so hex colors can be selected completely
remove # from word_separators, update year in LICENSE
@@ -5,5 +5,5 @@ | |||
{ "selector": "meta.mapping.key punctuation.definition.string.begin" }, | |||
], | |||
"extensions": ["sublime-color-scheme"], | |||
"word_separators": "./\\()\"':,.;<>~!@#$%^&*|+=[]{}`~?" // default without '-' | |||
"word_separators": "./\\()\"':,.;<>~!@$%^&*|+=[]{}`~?" // default without '-' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update comment, too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just did
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I do wish (now that I think about it) that you could have scope-sensitive word separators. Seems like a big ask of ST core, though.
Yeah, I don't think we'll be seeing that anytime soon... |
Thanks, let's hope this isn't too unexpected for users (since CSS doesn't do this either, at least at the moment). |
I removed
#
from the color schemeword_separators
so hex colors can be completely selected on double-click. I also updated the year in theLICENSE
to 2021. This will need to be changed again in 2 months. Maybe somebody can write an action for that...