Better documentation of configuration settings, bugs, and a feature request

[dougc84]

Hi - first off, great plugin. I love this thing.

After looking at the settings, I noticed a few things that don't have great documentation, and I want to request them to be added to the readme. Here's my list:

• What's the difference between style and ha_style?
• argb, icons_all, default_keybindings, and highlight_all don't have a lot of meaning. I can guess what argb and default_keybindings do, but, without diving into your code, they're difficult to understand.

Also, a couple bugs I've found:

• I cannot seem to get colored text to work in ST3 - is this the proper name for the ha_style value?
• I tried adding color_variables_file to my .sublime-project file, with an absolute path to my variables file. This also does not seem to work. My team is working on a UI redesign, and having this available would save a TON of SCSS compilation time and flipping back and forth between files.
• Also, +1 on the fix to not highlight variables with colors in their names (like $ui-purple-muted highlights the word "purple"), but you already knew that from the other outstanding issues. Removing "white" from the list of color_formats doesn't do anything.

Finally, one last feature request. We currently have an application that is deployed on several different domains. Each domain gets its own "variable override" file to style each domain properly - different colors, font sizes, etc., but the overall experience is similar. Because of this, it would be really great to make the color_variables_file into color_variables_files and accept an array of files. It would also need to (if it doesn't already), at least in SASS/SCSS, understand the !default modifier on variables. I believe LESS has a similar keyword.

Thanks for the great plugin!

[Monnoroch]

Great suggestion, thanks! If you want to speed things up, this is an open source project and I am always open to contributions and I'd love, if you'd be willing to help me with those. But in any case, I'll dig into the problem as soon as I can.

[Monnoroch]

Have made color_variables_file into color_variables_files.

[Monnoroch]

About the default. It seems to me, that do do that type of thing you have to use a full-blown less/sass parsers, which would totally kill the performance.

[Monnoroch]

You can always look for options names in the menu files.

{
     "caption": "Colored text",
     "command": "ch_set_setting",
     "args": {"setting": "ha_style", "value": "text"}
},

[Monnoroch]

About color_variables_file(s) not working: I could not reproduce the bug. Seems fine to me. If you could test the new version and provide a minimal example to reproduce the bug I'd be grateful.

[jacobbuck]

@dougc84 I was getting a similar problem with color_variables_files, turns out it was because I was putting it in the wrong place:

{
  "folders": [
    {
      "color_variables_files": [...],
      ...

When it should've been in the root level:

{
  "color_variables_files": [...],
  "folders": [
    {    
      ...