You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The keymaps at any given point for using the window are not obvious, and obfuscated through many layers
Describe the solution you'd like
most windowed neovim systems come with a mapping for '?' to show the currently available bindings at for the given state of the window/system.
currently, you cannot even go to the :h pages for the general bindings as it directs the user to the github wiki as a reference.
this is not helpful if the internet is down and a user would still like to make local commits etc.
Describe alternatives you've considered
I would consider maintaining the bindings list within the help docs much more intuitive for regular nvim users, since we are pushed early and often to seek out detailed information there about any individual system.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Did you check the docs?
Is your feature request related to a problem? Please describe.
The keymaps at any given point for using the window are not obvious, and obfuscated through many layers
Describe the solution you'd like
most windowed neovim systems come with a mapping for '?' to show the currently available bindings at for the given state of the window/system.
currently, you cannot even go to the :h pages for the general bindings as it directs the user to the github wiki as a reference.
this is not helpful if the internet is down and a user would still like to make local commits etc.
Describe alternatives you've considered
I would consider maintaining the bindings list within the help docs much more intuitive for regular nvim users, since we are pushed early and often to seek out detailed information there about any individual system.
Additional context
No response
The text was updated successfully, but these errors were encountered: