Simon Hauser

Overall Looks good. Thanks :)

try to run your command from cli with `--noplugin -u scripts/minimal.vim` the `minimal.vim` should only load your plugins and plenary I cant reproduce `PlenaryTestFile` issue thought

unless you do `require("plenary").path` rather than `require("plenary.path")` (`path` is here an example for any module) this shouldn't be an issue. We can still drop this thought, imo

plenary.path follows [pathlib](https://docs.python.org/3/library/pathlib.html) and `read` `write` is present there. Doesn't make sense to change it now after we stated that we somewhat follow pathlib. https://github.com/nvim-lua/plenary.nvim#plenarypath

> Don't call error. I don't think this commit actually solves the problem cited because the response is still attempted to be parsed after error is called. Calling error is...

Is this still relevant?

Did i underestimate the task? :) Or do you need any help?

Sounds good. We had it originally was not working good. Too much bloat sums it up great. Got replaced here: https://github.com/nvim-lua/plenary.nvim/pull/31 Can't wait for your draft :) Note you might...

We could add a option to disable the capturing. aka adding it to a table. So you only create on table, the one in `on_insert`

We have something similar for `plenary.job`. https://github.com/nvim-lua/plenary.nvim/blob/6bb0e09030a7c2af19bf288088ca815228de9429/lua/plenary/job.lua#L137-L144