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

Add VCS-based sidebar label coloring #217

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Conversation

alecmev
Copy link
Collaborator

@alecmev alecmev commented May 21, 2019

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, vcs_color setting enables the whole thing, vcs_color_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

image

@marcofugaro
Copy link
Collaborator

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

@alecmev
Copy link
Collaborator Author

alecmev commented May 26, 2019

@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
Copy link
Collaborator Author

alecmev commented Aug 27, 2019

Rebased to fix a conflict in readme.

@alecmev
Copy link
Collaborator Author

alecmev commented May 20, 2020

@marcofugaro

@alecmev
Copy link
Collaborator Author

alecmev commented Aug 11, 2022

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

@kkga
Copy link
Collaborator

kkga commented Aug 11, 2022

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

@alecmev
Copy link
Collaborator Author

alecmev commented Aug 11, 2022

@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
Copy link
Member

FichteFoll commented Aug 11, 2022

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
Copy link
Collaborator

kkga commented Aug 11, 2022

@alecmev any idea what this means?

image

@FichteFoll
Copy link
Member

FichteFoll commented Aug 11, 2022

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
Copy link
Collaborator Author

alecmev commented Aug 11, 2022

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
Copy link
Collaborator Author

alecmev commented Aug 11, 2022

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

@kkga
Copy link
Collaborator

kkga commented Aug 11, 2022

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

@FichteFoll
Copy link
Member

Indeed, all done on my part.

@kkga
Copy link
Collaborator

kkga commented Aug 11, 2022

Great, thanks all!

@alecmev
Copy link
Collaborator Author

alecmev commented Aug 11, 2022

Thank you! 👍

alecmev added a commit to alecmev/package_control_channel that referenced this pull request Aug 11, 2022
braver pushed a commit to wbond/package_control_channel that referenced this pull request Aug 11, 2022
@jakitliang
Copy link

jakitliang commented Feb 6, 2024

Is there any progress? @alecmev

@alecmev
Copy link
Collaborator Author

alecmev commented Feb 7, 2024

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.

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 this pull request may close these issues.

Git + sidebar + gutter Open files close icon margin issue after setting 'spacegray_fileicons:true'
5 participants