-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
[themes] Make folding indicator theme-able #172881
Comments
We have a setting to hide the folding twisty next to the line numbers. Is that helpful? |
Apologies for not being clear. By folding indicator I meant current placeholder for the collapsed text. The "..." that shows at the end of the folded line. |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
I admit that it is definitely a workaround (just like many things with the extension). It is just that changes of that size usually take a bit of time to be approved and merged, while adding this should be relatively simple (again, more than happy to provide a PR) and would go long way for the extension. It also comes with the benefit of providing one more thing users can personalize as well. |
The problem is really that colors come from themes. Your extension can not / should not overwrite that color. |
I agree 100% that my extension should not overwrite this. However, I would like to make the cases of:
Don't get me wrong, I understand that providing these features takes a lot of time and effort while at the same time joggling the rest of the backlog, and you guys doing more than an amazing job at it. All I'm asking is to allow us the extension authors to fill in the gaps in the meantime, and sometimes the only way we can deliver these requested features is using these hacky solutions. Of course they don't work for many cases, but a good enough hacky solution is much better than no solution at all. This was the long way of me saying: yes, my extension should not do this, but until #170447 gets merged, this might be our best alternative for now. |
So if we added that color, how would your extension set it to transparent? |
My initial thoughts are changing the workplace settings (like how vscode-peacock does it) to change the color to something with alpha value 0 (for example #00000000). Maybe even allow an option to make it apply to universal settings as well. I'm also thinking of having it apply on activate() and only on supported languages, and be removed on dispose() and while using unsupported languages. Of course all while making sure that users are aware of this and why we are doing it with an option to deactivate it and fallback to the current solution (with all its downfalls). |
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Verify that the new color |
Ah this isn't in insiders yet. |
Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting |
Documenting the new color I think we should rename the color to |
I'm currently working on the Better Folding extension, and would love to have the ability to customize the folding indicator's color.
My use case is simply setting the color's alpha to 0 to hide it, and show the customized collapsed text provided by the extension.
I am aware of #170447 (I am the author), but until that is merged, I could use this.
Would be more than happy to make the PR for this, just wanted to make an issue to see if there is any limitations I should know first.
The text was updated successfully, but these errors were encountered: