Anatolii Sakhnik

Thanks for the idea! But it's unlikely that I could get to it soon. Sorry.

Could you please reproduce the issue by launching Neovim from the plugin's directory `test`: `CI=1 ./nvim`? And provide me with the log files generated.

@kiddae, any updates on the issue?

No worries. I'd like to examine the log files to see how exactly the failure happens. So I'm asking to launch the debugger in a specific way, and then conduct...

Is `--args` a legitimate option? I don't see it in the gdb manual. I usually just launch `gdb binary`, then `run ` in the GDB CLI. Perhaps the error reporting...

Take your time. I will only be available after the war.

I haven't considered it. If delve's CLI has a distinct prompt, regular syntax for breakpoints lists, it is quite easy to hook it up. Would you try adding it as...

Thanks for the report! It looks like the prompt can't be recognized. Could you please run just one test like the following: `CI=1 ./run -vv 'test_10_generic.py::test_smoke[backend0]'` Then could you please...

This is really strange. I took the output of your debugger, and I see that the prompt is correctly recognized. I see you're using Gentoo with their build of neovim....

No worries, it's the Lua interpreter that does the parsing. Neovim is advertised to be using the quicker LuaJIT. And it has better support in Neovim too. So I'd suggest...