Hi! I'm using goose.nvim alongside LazyVim, and I've noticed a significant keymap conflict.
By default, LazyVim (and many other Neovim setups) uses g as the primary prefix for Git operations (specifically gg for lazygit). Since goose.nvim also defaults to gg for toggling the AI, it overrides the core Git functionality of the distribution.
Suggested Solutions:
- Change the Default Prefix: Consider changing the default prefix from g (Git) to a (AI) or G (Capital G).
- Opt-in Keymaps: Make the global keymaps optional via a config flag (e.g., use_default_keymaps = false) so users can define their own without having to manually delete the defaults.
- LazyVim Integration: Add a small note to the README on the recommended way to rebind these keys for LazyVim users.
Current Workaround:
I am currently manually unbinding the keys or setting default_global_keymaps = false in my setup, but a more "out-of-the-box" compatible default would improve the onboarding experience for many users.
Thanks for the great plugin!
Hi! I'm using goose.nvim alongside LazyVim, and I've noticed a significant keymap conflict.
By default, LazyVim (and many other Neovim setups) uses g as the primary prefix for Git operations (specifically gg for lazygit). Since goose.nvim also defaults to gg for toggling the AI, it overrides the core Git functionality of the distribution.
Suggested Solutions:
Current Workaround:
I am currently manually unbinding the keys or setting default_global_keymaps = false in my setup, but a more "out-of-the-box" compatible default would improve the onboarding experience for many users.
Thanks for the great plugin!