-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
console.log() crashes Nvim or exits node #329
Comments
|
Those write to stderr, not stdout, so they don't interfere with the RPC channel.
So our "monkey patching" of |
That's my guess too. |
This comment was marked as resolved.
This comment was marked as resolved.
2d47447 removed "sandboxing" and looks like it accidentally also removed the
|
This comment was marked as outdated.
This comment was marked as outdated.
Can you try #332 ? |
0.5.1 was released, can you confirm it fixes your issue @saidelike |
Nice I can confirm it works now! |
problem
Calling console.log() from the node plugin sends the data to nvim process. Because of this, it actually crashes the nvim process.
expected behavior
Calling console.log() from the node plugin should just log.
details
for instance with the code:
I attach to nvim and set a breakpoint on the following line https://github.com/neovim/neovim/blob/a4290f462ed7dc81e17b09bd27877b106b24b6bd/src/nvim/msgpack_rpc/channel.c#L304
for instance I use this breakpoint on Windows. we can see below that nvim receives the data that we try to log with
console.log
. Also note that it doesn't receive the data that we log withconsole.warn
:At the end the problem I was describing in neovim/neovim#23781 (comment) was due to me using
console.log
...The text was updated successfully, but these errors were encountered: