Added configurable color selector

[cibinmathew]

Added configurable color selector while defining commands/hotkeys. Previously a random available color was used. Now one can specify the color(colors are mapped based on scope)

{
    "keys": [ "ctrl+super+j" ],
    "command": "text_highlighter_toggle",
    "args": {
        "color": "markup.changed.git_gutter" <----additionaly specify the color argument
    }
}

[cibinmathew]

@kdnk do you suggest adding more information on colors available

[kdnk]

@cibinmathew Thanks for creating this PR 🙂
Could you write some description about these changes?

[cibinmathew]

@cibinmathew Thanks for creating this PR 🙂 Could you write some description about these changes?

Updated

[kdnk]

@cibinmathew Thanks!

[kdnk]

@cibinmathew

• Do you mean we can pass only one color?
  • I think it might be more useful if we can pass a list of colors (and override the existing colors_by_scope), which means users can use any color they want.
• You've mentioned https://www.sublimetext.com/docs/scope_naming.html, but will this PR work even if we pass some scope_naming that isn't defined in colors_by_scope?
  • Not sure, but I guess we might get an error at

    sublime_text_highlighter/highlighter.py

    Line 66 in e0991eb

    if not colors_by_scope[color]:

    .

[cibinmathew]

This PR would work only for the 9 listed scopes in

sublime_text_highlighter/highlighter.py

Lines 124 to 134 in e0991eb

	colors_by_scope = OrderedDict() # TODO: Make color configurable
	colors_by_scope['markup.changed.git_gutter'] = None # vivid purple
	colors_by_scope['support.class'] = None # yellow
	colors_by_scope['markup.deleted.git_gutter'] = None # vivid pink
	colors_by_scope['markup.inserted.git_gutter'] = None # vivid green
	colors_by_scope['constant.numeric'] = None # orange
	colors_by_scope['constant.character.escape'] = None # light blue
	colors_by_scope['variable'] = None # red
	colors_by_scope['string'] = None # light green
	colors_by_scope['comment'] = None # glay

I have added the list of the scopes in Readme. Probably can work on another PR later to add support to more scopes/colors.

[cibinmathew]

@kdnk available colors

[kdnk]

I realized that readme😄. But I meant users can still path any scopes, and it might cause runtime errors if users passes scopes which are not listed on the readme. Am I missing something?

[kdnk]

But... the current implementation might be sufficient😄 If we have proper safeguards in place for cases where users use non-listed colors, the plugin will still not work.

[kdnk]

Thanks!!!