-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Need option(s) to remove (less useful) status bar indicators #3874
Comments
Any updates on this? Would be super nice to be able to hide some items! ✌️ |
@Tsourdox as a temp solution, I'm doing the following:
Using this plugin for custom css: There are a few more items that can be hidden, but those were among the few which had css classes. Hope that useful. |
Why we always need to know the current tab size in the status bar escapes me. |
At the very least, we should be able to click and drag to rearrange the items. I have 18 different items sitting in my status bar and some of them are far more useful than others. |
One possible solution would be to have a setting to control what installed extensions are allowed to create status bar items. For example, it would be nice if it was possible to disable status bar items created by the Live Share extension but not the Python extension. |
My idea was to be able to configure a number-weighted priority system for status bar items, so if the window becomes too small to display all the items, the ones with lower priority would be removed first. |
@ryansully Who decides the priority? |
@lonix1 Priority would be user-configurable, so the user would rank status bar items as they see fit. |
To add to the above comment, a default priority (e.g. 0) could be assigned to every status bar item all status bar items, and the user could override the priority for each item/extension in their settings. |
Could you guys stop commenting on this unless you have something useful to add? Spoiler alert: you have no new information to add unless you're a Microsoft employee and commenting on this sends and email to hundreds of subscribers! Please cease your commenting. |
"Me too" comments aren't helpful. |
I see three potential solutions here: The Firefox method: toolbar items can be dragged and dropped to rearrange, and any that the user wants to hide can be dragged into an overflow menu. This has the advantage of making all items easily accessible at all times, but because they are different widths, an overflow menu of the items would be awkward. The Windows method: items can be dragged and dropped to rearrange, and shown/hidden with checkboxes in a context menu. This means that the user could hide an item and totally forget it exists, but this may be desired by many. Finally, if just dragging and dropping items is allowed, the window could simply hide the items in the middle first as the window is resized. |
Pushed an initial version to master that works very much like our existing UI for showing/hiding views: Limitations:
Feedback welcome (will be in insiders tomorrow). |
I built the Status Bar Tasks extension to solve I problem I was having getting VS Code Tasks to fire off quickly.
https://marketplace.visualstudio.com/items?itemName=GuardRex.status-bar-tasks
I've noticed recently that default (less useful to me) status bar indicators are taking up a lot of real estate in the status bar on my laptop (smaller screen width than my PC monitor), so I can't fit all of my Tasks in the status bar on my laptop.
I'll ask over in the OmniSharp repo about removing the word "Running." Having indicators for the spacing, character set, end-of-line sequence, language mode, and feedback icon are totally useless to me and can be accessed easily enough via the cmd palette ...
I don't see anything on SO or in the docs on how to turn some or all of these indicators OFF. If it can't be done currently, may I suggest workspace option(s) as a feature to remove some/all of them (the VS Code ones anyway ... I understand third party ones would need to be addressed by those vendors)?
The text was updated successfully, but these errors were encountered: