Iordanis Petkakis

https://github.com/folke/snacks.nvim/issues/1644#issuecomment-2758908856

`snacks.nvim` already provides a `projects` feature, so most likely the plugin `project.nvim` will just be removed from Extras and not replaced with another one. Users can of course add whatever...

`copilot.lua` states that it requires Neovim >=0.10, so try upgrading Neovim first. > Requirements Curl NeoVim 0.10.0 or higher This also is not Lazyvim related, but Copilot, so create an...

I created https://github.com/zbirenbaum/copilot.lua/issues/436, which is about this issue, so better follow up on that. Depending on the answer I get on that issue, only thing LazyVim can do is remove...

Should be fixed upstream as stated in the issue I opened in Copilot repo. Update the plugin.

#5900 should fix that. Instead of you waiting for the PR to merge you can look at #5899 and specifically [this comment](https://github.com/LazyVim/LazyVim/issues/5899#issuecomment-2781398031) to apply the change locally. After the PR...

Just did a fresh LazyVim installation and both issues mentioned here (initial from OP which is actually a Copilot issue and with the lualine which is a LazyVim configuration issue...

`colorscheme` can be a function. So, you can do something like ```lua colorscheme = function() vim.schedule(function() if vim.o.background == "light" then vim.cmd("colorscheme catppuccin-latte") else vim.cmd("colorscheme tokyonight-moon") end end) end ```...

The `` keymap gets defined in `coding.lua` as you pointed out but for specific modes as can be seen [here](https://github.com/LazyVim/LazyVim/blob/12818a6cb499456f4903c5d8e68af43753ebc869/lua/lazyvim/plugins/coding.lua#L113). So, when you disable it you also have to define...

See #3302 and also [this comment](https://github.com/LazyVim/LazyVim/discussions/5186#discussioncomment-12090959) and do something similar in your personal configuration. Something similar was asked in the past, but maintainer was not willing to implement it, since...