not working with neovim

[scampi]

I get the following error when I run :nbs with neovim.

E319: Sorry, the command is not available in this version

Do you know how I can resolve this ?

[sidorares]

https://github.com/neovim/neovim/wiki/Introduction#legacy-support-and-compile-time-features

Looks like netbeans server is not supported in neovim. Possible solutions: write netbeans server plugin ( I tried that with Atom editor by the way, the protocol is very simple ) or explore other means of connecting and write adapter on vim-debugger side

[sidorares]

https://github.com/neovim/neovim/blob/master/runtime/doc/remote_plugin.txt#L7

[sidorares]

The functionality I'm currently using via netbeans protocol: open a buffer in vim, listen for keys, set gutter marker ( current line and breakpoints )

[sidorares]

so I can see two options here: 1) implement neovim api <-> netbeans proxy at network level ( app that talks netbeans protocol on one side and neovim on other side ) or 2) make a library on top of netbeans and neovim clients and use common api

https://github.com/neovim/node-client/blob/master/index.d.ts

note that neovim api seems to lack gutter functions ( addAnno vim-netbeans function ). This could probably be solved by executing a number of native vim commands

[Anzumana]

we need to reopen this issue. i will try to talk to some people in the neovim community and see what they think about the issue. otherwise possible roadmap goal.

@anchnk had the same issue with neovim 0.2.2

[sidorares]

@Anzumana the design in mind was to allow multiple types of pluggable editor drivers ( currently only netbeans but we could also add neovim-specific ) and multiple debugger drivers ( currently only V8 debugger protocol but we can add CRD, java debugger, Xdebug / other over the wire debuggers )

[JulioJu]

It could be very, very cool !

[nguyennb9]

I found this is the only result about the :nbs in neovim, hope to see some update :)

[sidorares]

@nguyennb9 feel free to help :)

[nguyennb9]

Oh, last commit 2 years ago, let me see how I can help.

[sidorares]

Biggest help would be to switch from v8 debugger protocol ( that is no longer supported by node ) to a Chrome Devtools Remote protocol ( this is what node uses when you start --inspect )

[T-vK]

In the meantime you could take a look at https://github.com/eliba2/vim-node-inspect which supports neovim and the new --inspect protocol.

[sidorares]

Thanks @T-vK , never heard about it