Simon Hauser

attach_mappings SHOULD not be used like this! it would make more sense to consistently support user autocmds for all points where ppl want to inject custom functions OR implement a...

Also experiencing this issue in 5.0.0. The codepen for reproducing also still seems valid, you just have to replace the version, none the less should i open a new issue?

I think this has something to do with luarocks support in lazy.nvim. we have a rockspec file for quite sometime and lazy.nvim now tries to install plenary with that rockspec...

sorry was on mobile earlier. lazy has rocks support, not plenary. so try ```lua { "nvim-lua/plenary.nvim", name = "plenary", rocks = { enabled = false, }, }, ```

no sorry, previous example was also wrong. ```lua require("lazy").setup({ rocks = { enabled = false, }, { "nvim-lua/plenary.nvim", name = "plenary", } } ``` this should have nothing to do...

thanks for confirming. so its a breaking change in lazy.nvim that can cause problems with plugins that provide a rockspec file. Not related to this repo. closing

Would be good to know when the error is happening. What are you calling? What is your config. Just anything ....

plenary itself only provides a curl library, we dont actually use it. so might be a misuse of the library or we have a bug. can you share which plugins...

we are having the same issue with flake8=4.0.0. Because this is a blocker for me right now i forked the repo and done the appropriated changes to make it work...

We still have some jit stuff in `plenary.path`. I will remove them as soon as possible and make sure Lua 5.1 works. But it will not work as good as...