Skip to content
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

issue: Lazy UI hardcoded title key indicator for Home section. #1796

Open
4 tasks done
Aumnescio opened this issue Nov 1, 2024 · 0 comments
Open
4 tasks done

issue: Lazy UI hardcoded title key indicator for Home section. #1796

Aumnescio opened this issue Nov 1, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Aumnescio
Copy link

Did you check docs and existing issues?

  • I have read all the lazy.nvim docs
  • I have updated the plugin to the latest version before submitting this issue
  • I have searched the existing issues of lazy.nvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

NVIM v0.10.2

Operating system/version

Pop!_OS 22.04 LTS

Describe the bug

When changing a Lazy UI keybinding like "<S-h>" -> Home, the title does not adapt to this change, as it is hardcoded at lua/lazy/view/render.lua:148. ( title = " lazy.nvim (H) " )

This does not appear to be the case for all the section titles. For example, the Install section's title was updated properly.

Steps To Reproduce

The only way I managed to change these keybindings was to do:

require("lazy.view.config").commands.home.key = "W"
require("lazy.view.config").commands.install.key = "E"

I'm not quite sure if it's supposed to be possible to change these bindings through the custom_keys table, but my attempts were not working.

Expected Behavior

The Home section's title "lazy.nvim (H)" should adapt to the currently bound key, like the Lazy UI Help section does.

Using require("lazy.view.config").commands.home.key = "W", the title should be "lazy.nvim (W)".

Repro

No response

@Aumnescio Aumnescio added the bug Something isn't working label Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant