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.
In the lazy buffer you can open the commit under the cursor in the browser using K. K is referred to as hover in lazy code base and is a default mapping for lsp hover behaviour that does not take an user out of current buffer.
While this has been the case in lazy.nvim for as long as it has been around. I still stumble over it to this day and presume there are more users with this problem.
Describe the solution you'd like
It would be great if lazy.nvim would also set a keymap wrapper for gx for the lazy buffer to be able to open commits using the native key map to open something in the browser.
Describe alternatives you've considered
I can fix this for myself by adding a lazy buffer only key map for gx. But thought I would highlight it here as more people may stumble over it as I do.
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.
In the lazy buffer you can open the commit under the cursor in the browser using K. K is referred to as hover in lazy code base and is a default mapping for lsp hover behaviour that does not take an user out of current buffer.
lazy.nvim/lua/lazy/view/config.lua
Line 30 in aa1c957
While this has been the case in lazy.nvim for as long as it has been around. I still stumble over it to this day and presume there are more users with this problem.
Describe the solution you'd like
It would be great if lazy.nvim would also set a keymap wrapper for gx for the lazy buffer to be able to open commits using the native key map to open something in the browser.
Describe alternatives you've considered
I can fix this for myself by adding a lazy buffer only key map for gx. But thought I would highlight it here as more people may stumble over it as I do.
Additional context
No response
The text was updated successfully, but these errors were encountered: