suketa

I found nvim-dap-ruby works fine with nvim-dap older version (Feb 4, 2022). But I don't know what is the breaking change now. I'll investigate more.

I found nvim-dap-ruby works fine with nvim-dap with commit https://github.com/mfussenegger/nvim-dap/commit/1de5f63228488fef93af22448ba2febad71a3a4f but nvim-dap-ruby does not work well after commit https://github.com/mfussenegger/nvim-dap/commit/4446d77b75b41bae89a7d6d845f72333dcaba86a I'll investigate more.

I think it is expected behavior. Could you try the following after break at the beginning of file execution? 1. :lua require'dap'.repl.open() 2. move cursor into opened buffer 3. type...

I think https://github.com/mfussenegger/nvim-dap/pull/553 will fix this issue. And https://github.com/suketa/nvim-dap-ruby/pull/12 will stop at breaking point at first. Could you try ~~https://github.com/mfussenegger/nvim-dap/pull/553~~ latest nvim-dap, nvim-dap-ruby ?

I can't reproduce the behavior you said. Could you show me the simple spec file to reproduce it?

@DannyBen Sorry, but I'm not a duckdb creator nor OS packages maintainer. I don't have any plans about it. You should ask duckdb creator or OS packages maintainer. I hope...

@sandstrom Thank you for your suggestion. I started github sponsors. I can't promise anything and I don't have enough time to improve this gem. But I will keep maintain this...

related issue #561, https://github.com/duckdb/duckdb/issues/9475

I'm not sure, but could you check to set breakpoint? If you don't set breakpoint, then ruby debugger runs completely *_spec.rb and terminated normally.tr After ruby debugger terminated, nvim try...

@stephenprater I'd like to know there are some breaking changes or not. If there are some breaking changes, pls explain me about the detail.