Iordanis Petkakis

It seems that if you set any kind of `version` in your `lazyvim.json` there's no issue. Conversely, if you change [this line](https://github.com/LazyVim/LazyVim/blob/12818a6cb499456f4903c5d8e68af43753ebc869/lua/lazyvim/util/json.lua#L66) to be like [this one](https://github.com/LazyVim/LazyVim/blob/12818a6cb499456f4903c5d8e68af43753ebc869/lua/lazyvim/util/json.lua#L71) the problem doesn't...

@saxon1964 I'm just a simple user with very limited programming knowledge as a hobby of mine. I'm not a programmer. I haven't even looked at `snacks.image` code because it's too...

@saxon1964 https://github.com/folke/snacks.nvim/issues/1644#issuecomment-2758908856 So, we have to be patient until mid May.

If you press `` to cycle through to the list window, then if you put your cursor over a commit sha and press `gB` it will do what you want....

This will also close #393, which I believe is better to expose `commit` in `opts` if it's something that the maintainer would consider adding.

I personally can't repro even without the mentioned PR any more. Don't know when it stopped being a problem, since I use Neovim native snippets engine by default. I only...

@iamxiaojianzheng No need to rush things. Please be patient. Either way it's something that you can easy integrate into your autocmds until this gets merged.

The error comes from `nvim-navic` itself. Probably related to this [PR](https://github.com/SmiteshP/nvim-navic/pull/153/files). Should be `vim.fn.has("nvim-0.11") == 1` in the check. There's also a PR https://github.com/SmiteshP/nvim-navic/pull/157 to fix that, but hasn't been...

Couldn't you just use `vim.fn.executable` in `keymaps.lua` instead of the helper util function?

Why? Those are default Telescope mappings. Nothing to do with Lazygit.