Closed duarm closed 8 months ago
Using nil
would be tricky and a breaking change, since it can be used to unset a property.
false
can be a regular value, so it's also not suited.
I instead added a dap.ABORT
constant that can be used for this. See https://github.com/mfussenegger/nvim-dap/pull/1079
Problem Statement
Not sure if this is a dap-ui or dap problem, I have this in my configuration
the problem is that if I start the debugger, I get prompted by the vim.fn.input function, if I change my mind, there's no way out, trying to close the input via esc still launches the ui, even when nil or false is returned by
program
, resulting in everything being broken, is there a workaround for that? I want to abort dap completely by returning something like nil or false.Possible Solutions