Closed Climax777 closed 10 years ago
Startup process is currently manual multi step, you need to follow as per readme:
node --debug yourscript
or node --debug-brk foo.js
or coffee --nodejs --debug-brk bar.coffee` )./bin/vim-inspector.js
) - it starts listening vim-netbeans connections and connects to debuggervim -nbs
or from existing session type :nb
in command mode. On connection, vim-inspector sets key handlers via vim-netbeans protocol I'm currently have version which does all this in one go (spawn script & agent & vim in right order ) but it's not quite ready yet
I manage to get vim running, showing an arrow next to the line (at startup due to --debug-brk), but none of the shortcut keys work. I've removed my custom .vimrc/ and .vim/ and tried again, but no luck.
Are there no settings or plugins I'm missing?
The arrow is not moving, and breakpoints show nothing and don't trap the code. (Ctrl+c seems to work but there is no feedback of it other than my node program running)
Okay, I pulled master and it seems to work now.
Hi
I'm having trouble with using the debugger in vim. Should I map the keys somehow?