NInspect neovim

[ColinRyan]

Hey, I'm trying to use vebugger with neovim and Nodejs. Whenever I run the command to start the debugger it opens a new split and then closes it.

Any ideas what I might be doing wrong and does this plugin have any logs or messages for debugging such issues? Thanks :)

[daniellmorris]

Do you have a breakpoint set? Is your application one that would stay open for a long period of time? It sounds like it is ending immediately...or it could be something else.

[ColinRyan]

So, I was able to get it working after. Turns out the problem wasn't that the debugger wasn't working, but it's that it won't work if the breakpoint is on the first line. I'm testing this with node.js. Any idea of what might cause that?

[TerminalWitchcraft]

Facing the same issue here, when debugging node apps inside vim, a terminal buffer quickly opens and closes.

[nilsboy]

FYI
I use these changes to vim-vebugger/autoload/vebugger.vim to see what nodejs does:

"Close the terminal buffer
function! s:f_debugger.closeTerminalBuffer() dict
  return
    if has_key(self,'terminalBuffer')

"Create a debugger and set it as the currently active debugger
function! vebugger#startDebugger(command)
    call vebugger#killDebugger()
    call s:f_debugger.showTerminalBuffer() 

    let s:debugger=vebugger#createDebugger(a:command)