-
Notifications
You must be signed in to change notification settings - Fork 12
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
Feature request: Add the ability to go full width and dock to the editor #59
Comments
That looks really good 👍 |
This seems a nice change :) |
Maybe we can make this configurable to some extend 🤔
You can adjust the font size as well as some other appearance related parameters. See the README here |
Sorry for the delay in responding to this, I've been very busy with work. On that note - I've been using my fork of this for the past 2 weeks with 0 issues. @qrzychu I took a look at the layout options provided by which-key.nvim. Here's what they offer:
Would you be happy with having the same set of options? That would give you the ability to center the content of the popup. @TheBlob42 What are your thoughts on this? |
Sounds good to me 🙂 if it is easy to implement go for it. From my memory it should now be possible to use "dictionaries" in the Would love to see a PR so I can easily compare how you implemented your changes. |
is there a chance this is getting implemented? |
@mattrcullum are you still interested in this feature and do you have the time and capacity for implementing this? 🙂 |
The emacs/vim which key plugins both take up the full width of the screen and are docked in the editor whereas idea-which-key seems to always have right margin and is not docked within the editor.
Would there be any interest in a PR that adds the ability to make idea-which-key behave more similarly to the emacs/vim variants?
For reference, here's the way emacs behaves
And here's idea which key
I know it's a relatively small thing but aestethics really matter to me and I would be happy to do the work if there's interest.
The text was updated successfully, but these errors were encountered: