Add VCS-based sidebar label coloring

[alecmev]

Essentially a copy-paste from Toxin, thanks @p3lim! One divination is that I chose to decolor the VCS badges, instead of outright hiding them, since they help distinguish created/modified from staged. Another is the italic for ignored files, which I wouldn't mind dropping, but it's somewhat useful.

Didn't know what colors to choose, so just looked at VS Code's Base16 Themes.

This is opt-in, spacegray_sidebar_vcs_label setting enables the whole thing, spacegray_sidebar_vcs_expanded also applies the coloring to expanded folders. The latter one is the same setting name as in Toxin, for potential interop.

Added variables introduced in 3179, because why not. Opted not to indent the rules as to not ruin the diff for the main feature and to not pollute the blame trail. base prefix because reasons.

Also piggybacked in a fix for #188, since the original PR has died a slow and painful death.

Fixes #214
Fixes #188

[marcofugaro]

Thanks for the contribution! Will test this locally and review the changes!

[alecmev]

@marcofugaro Took a closer look at the other themes, besides Eighties, and yeah, those needed tuning, especially Light. Also got rid of the selected effect, doesn't look good, and isn't really necessary.

[alecmev]

Rebased to fix a conflict in readme.

[alecmev]

@marcofugaro

[alecmev]

@kkga @marcofugaro Hi! I'm willing to adopt this theme. Could fork, but I don't intend to change much, just modernize.

[kkga]

@alecmev hey! Thanks for your interest. Do you want to move this repo to community packages org?

[alecmev]

@kkga Yeah! I haven't coordinated with them yet though. I think you need to be a part of an organization to be able to transfer to it. You can transfer to me, and I can take care of the rest, what do you prefer?

[FichteFoll]

Hello, I am your person of contact for moving packages to the SublimeText org.

Your assessments have been correct so far. The person moving the repo needs to be a part of the org and since @alecmev volunteered to take maintainership, I invited him. I suggest the following procedure

1. @kkga transfers the repo to @alecmev
2. @alecmev transfers the repo to the org
3. @alecmev updates the reference to the package in the package_control_channel via a PR
4. In the meantime, I configure the permissions for the moved repository

From then on, you are free to do whatever you would if the package hadn't been moved, i.e. push new updates by creating a new tag.

[kkga]

@alecmev any idea what this means?

[FichteFoll]

Ah, I suspect that is because of an already existing fork. I didn't think of that.

You may also transfer the repo to me and I will take care of transfering it to the org.

[alecmev]

Ah, I suspect that is because of an already existing fork. I didn't think of that.

Indeed! I renamed the fork to spacegray-fork ahead of it, but that didn't help.

You may also transfer the repo to me and I will take care of transfering it to the org.

I already submitted a "detach a fork" request to GitHub, but this is faster, thanks for offering! @kkga Can you transfer to @FichteFoll instead, please?

[alecmev]

@kkga The fork has been detached, just in case, so you can transfer to me too 😉

[kkga]

The transferto @FichteFoll is already in progress. Just waiting for them to accept I think.

[FichteFoll]

Indeed, all done on my part.

[kkga]

Great, thanks all!

[alecmev]

Thank you! 👍

[jakitliang]

Is there any progress? @alecmev

[alecmev]

Didn't realize there was demand, will try to clean up and release soon. This isn't ready as-is yet, unfortunately, as I've noticed some inconsistencies between dark/light in personal use.

[FichteFoll]

I took a brief look at the contents here (as a result of #221) and have a small question.

[FichteFoll]

Thanks for sticking to it. I have released 1.4.0 with these changes.

Feel free to do changes on your own in the future (via pull requests or directly).

[alecmev]

Thanks for taking care of this!