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

bug: can't work with snacks.nvim #896

Open
4 tasks done
rogtino opened this issue Nov 26, 2024 · 0 comments
Open
4 tasks done

bug: can't work with snacks.nvim #896

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

Comments

@rogtino
Copy link

rogtino commented Nov 26, 2024

Did you check docs and existing issues?

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

Neovim version (nvim -v)

NVIM v0.11.0-dev-1228+g9e7b0bcf51

Operating system/version

5.15.167.4-microsoft-standard-WSL2

Describe the bug

g does not work in dashboard,remove which-key resolves this.

Steps To Reproduce

press g in dashboard does not open lazygit

Expected Behavior

lazygit window should open at once.

Health

which-key:                                 require("which-key.health").check()

- OK Most of these checks are for informational purposes only.
  WARNINGS should be treated as a warning, and don't necessarily indicate a problem with your config.
  Please |DON'T| report these warnings as an issue.

Checking your config ~
- WARNING |mini.icons| is not installed
- WARNING |nvim-web-devicons| is not installed
- WARNING Keymap icon support will be limited.

Checking for issues with your mappings ~
- OK No issues reported

checking for overlapping keymaps ~
- WARNING In mode `n`, <g> overlaps with <gx>, <gri>, <grr>, <gra>, <grn>, <gO>, <g%>, <gc>, <gcc>:
  - <g>: Dashboard action
  - <gx>: Opens filepath or URI under cursor with the system handler (file explorer, web browser, …)
  - <gri>: vim.lsp.buf.implementation()
  - <grr>: vim.lsp.buf.references()
  - <gra>: vim.lsp.buf.code_action()
  - <grn>: vim.lsp.buf.rename()
  - <gO>: vim.lsp.buf.document_symbol()
  - <g%>: Cycle backwards through results
  - <gc>: Toggle comment
  - <gcc>: Toggle comment line
- WARNING In mode `n`, <gc> overlaps with <gcc>:
  - <gc>: Toggle comment
  - <gcc>: Toggle comment line
- OK Overlapping keymaps are only reported for informational purposes.
  This doesn't necessarily mean there is a problem with your config.

Checking for duplicate mappings ~
- OK No duplicate mappings found

Log

Debug Started for v3.13.3
{
  branch = "main",
  commit = "b9684c6ec54d8a8452bdcf0d613c7ad0223fc3fe"
}
new Mode(n:1)
Trigger(add) Mode(n:1) ` ' " z= g` g' z ] [ <C-W> gr
on_key: g
on_key: j
BufNew(4)
BufEnter(4)
  new Mode(n:4)
BufNew(5)
ModeChanged(n:nt)
  Safe(true)
ModeChanged(nt:t)
  new Mode(t:4)
  Safe(true)
Trigger(add) Mode(n:4) ` ' " g` g' z= g ] [ z <C-W>
on_key: q
BufEnter(1)
ModeChanged(t:n)
  Safe(true)
on_key: q
BufNew(6)
BufEnter(6)
  new Mode(n:6)
Trigger(add) Mode(n:6) ` ' " g` g' z= g ] [ z <C-W>
on_key: :
ModeChanged(n:c)
  new Mode(c:6)
  Safe(true)
Trigger(add) Mode(c:6) <C-R>
on_key: q
on_key: <CR>
ModeChanged(c:n)
  Unsafe(command-mode)
  suspend: Mode(n:6)
  Trigger(del) Mode(n:6) ` ' " g` g' z= g ] [ z <C-W>
Trigger(add) Mode(n:6) ` ' " g` g' z= g ] [ z <C-W>

Repro

vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

vim.o.timeout = false
require("lazy.minit").repro({
	spec = {
		{ "folke/which-key.nvim", opts = {} },
		{
			"folke/snacks.nvim",
			priority = 1000,
			lazy = false,
			opts = {
				dashboard = {
					enabled = true,
					preset = {
						keys = {
							{
								icon = "",
								desc = "Git",
								action = function()
									Snacks.lazygit()
								end,
								key = "g",
							},
						},
					},
				},
			},
		},
	},
})
@rogtino rogtino added the bug Something isn't working label Nov 26, 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