-
Notifications
You must be signed in to change notification settings - Fork 17
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
Bigger or multi-column menu? #37
Bigger or multi-column menu? #37
Comments
Thank you for liking the extension. You are right that we certainly limited by what we can do with the vscode API. The QuickMenu is what we use to render to list; we don't have many options to customize it. Multiple column, and location of the location of the QuickPick are not customizable. However, a long shot is to experiment with something like a (custom web view)[https://code.visualstudio.com/api/extension-guides/webview] in the bottom pane. However, my gut sense is that the challenge would be shifting the focus back to where it was. An other alternative could be trying out the sort option in which-key config that might help discoverability. We can also implement a custom sort option that shows command binding first. |
I closed this by accident. |
Thanks for the quick reply! FWIW I managed to find a workaround for this, based on microsoft/vscode#85374. It's an ugly workaround using Customize UI, which then uses Monkey Patch which patches VS Code's code when it's launched... Not saying I'm happy about it, but now I can do: "customizeUI.stylesheet": {
".quick-input-widget > .quick-input-list > .monaco-list": "max-height: none !important;"
}, and get: so I guess if it's stupid and it works, it ain't stupid 😉 |
That's awesome!! Multi-column might possible with some more css magic, but I assume arrow keys are going to be weird with multi-column. @The-Compiler Wondering would you mind documenting your workaround to https://github.com/VSpaceCode/vspacecode.github.io/blob/master/docs/bonus.md? And we can close out this issue. |
I can do that! (Though I might be away for a couple of days first.) Should that really be in |
That makes perfect sense :) |
I'm still tinkering with this some more before adjusting docs. Multi-column is definitely possible with some more CSS injection: but it pretty much breaks other quick inputs: would be great to only apply it to quick inputs coming from vscode-which-key, but I don't see a way to tell them apart. |
That very impressive. Yeah, I am not sure what we can do since we don't control the rendering and I also assume the quickpick menu css is shared across different menu. Btw, how did you get different colors text? |
For reference, here's the setting for the (rather buggy) three-column menu: ".quick-input-widget > .quick-input-list .monaco-list-rows":
"display: grid !important; grid-template-columns: repeat(3, 1fr); grid-auto-rows: 1.5em;",
".quick-input-widget > .quick-input-list .monaco-list-row":
"position: unset !important;", As for the text colors, that's yet another hack just matching text starting with a ".quick-input-widget > .quick-input-list .monaco-list-row[aria-label*=\" +\"] .label-description":
"color: #8ec07c !important;", and the icon styling: ".quick-input-widget > .quick-input-list .codicon":
"color: #83a598 !important; padding-right: 8px;", |
Okay, I'm giving up on the multi-column thing, I don't see a way to do this without breaking all other quick inputs unfortunately. Time to add the height workaround to the docs then! What branch should I open a PR for, though? Should I use the |
That's a bummer, but it looks really cool tho. Since this is not tied to any version, I don't think it needs to be on the refactor branch. We have |
Problem
When I press space, I don't immediately see all possible keybindings:
Solution
Either showing the possible options in multiple columns; or at least extending the overlay to the bottom of the window.
I have no idea if either of those are possible, though, as I assume the overlay is displayed by VS code, not manually by the extension.
Alternatives
Scrolling manually to see all possible keys. Maybe there's a way to customize this already, but I didn't find anything after looking through the docs and VS code settings.
Additional context
Thanks for the extension! ❤️ This makes me seriously consider to switch away from Emacs (with Spacemacs and later Doom emacs) after some years, because I never really got the hang of it, but I love the concept!
The text was updated successfully, but these errors were encountered: