Iordanis Petkakis

Regarding `render-markdown`, `lazy.nvim` parses all the files alphabetically and adds to the plugin specs. `lazyvim.plugins.extras.coding.avante` comes before `lazyvim.plugins.extras.lang.markdown`. A workaround would be to change the priority of the Markdown Extra....

`optional` only means "add this spec if there's already a base spec present somewhere else". At the same file you will see somewhere at the end that the table `extras`...

I saw that you removed the `lang.markdown` priority. Was that intentional? Did you find another way to make it work without that addition?

So, does `grug-far` and `rustaceanvim` and possibly other plugins I'm not aware of. Honestly, I really don't see any reason for users to still be using Neovim 0.9.* when 0.10.1...

@georgeguimaraes I just created #4506 for `render-markdown`. After a recent commit, it's not necessary any more to define both Lazy's `ft` and the plugin's `opts.file_types`. I opted in to get...

Oh ok. I haven't used it, so i'll leave that to you. Then maybe you'd also like to leave the `lang.markdown` with higher priority to make sure it gets loaded...

There are currently 30 PRs open and maintainer seems like he has a lot of load and attention to the new `Snacks.picker` he just released trying to weed problems out....

Testing this locally if we change this line https://github.com/folke/lazy.nvim/blob/ac21a639c7ecfc8b822dcc9455deceea3778f839/lua/lazy/core/fragments.lua#L166-L166 to ```lua if plugin.specs and plugin.enabled ~= false then ``` seems to be working (at least with the minimal repro that...

It seems to have to do with the fact that `neoscroll.nvim` is also defined as a spec in `nui.nvim`. If you comment out ```lua { -- only configure some neoscroll...

But this doesn't happen if neoscroll isn't defined as a spec in `nui.nvim`. The children in that case do get ignored. It has to do with the fact that the...