-
Notifications
You must be signed in to change notification settings - Fork 7
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
The verbose status bar #9
Comments
That's really a concise idea. I like it. Actually I was tangling about the long status bar and two switches for a while. |
Also... Could have a setting to hide the status bar commands too? |
Hey @moxwel, thanks for the advice. For clarifying your requirement, does it mean that you want to have a setting to hide the items in the status bar but leaving the commands so that the mode can be switched in the "Show All Commands" menu or shortcuts? |
Exactly! Only hide the items in the status bar. |
Hiding the status bar items would be nice. But an even better option would be: {
"synchronizedScrolling.statusbarItems": "show", // or "hide" or "showWhenEnabled"
} The And of course you could hide the items with |
Hi @contributorpw after so long time, a new patch version (v1.3.1) published, please check it out. It took your advice that merge the two menubar items into one. Now it only has one button to change the different modes with the three options 😃 |
Hi @lonix1 , thanks for your advice, for now there is always a workaround that you can disable the extension in your vscode and all the related items will not display. |
@dqisme , thanks so much! I'm using this ext sice microsoft/vscode#33110 (comment) That's cool! |
I think that the status bar of the extension is redurant.
As you can see it is placed over a sufficiently long space.
My suggestion is to reduce the status bar to a few characters. For example
Also if this can be view I think if the Sync Scroll NORMAL/OFFSET is activated then Sync Scroll should be enabled programmatically.
Please review the issue and let me know what you think and hat you prefered in a PR (if there is a need for it).
The text was updated successfully, but these errors were encountered: