Open saidelike opened 3 months ago
Not sure how this is different from https://github.com/neovim/node-client/issues/342
ALLOW_CONSOLE=1
by definition will break a RPC channel because the "console" is stdout, which is also the RPC channel.It's documented at https://github.com/neovim/node-client?tab=readme-ov-file#logging but I'll make it clearer.
We could try writing to stderr instead of stdout.
As detailed in https://github.com/neovim/node-client/issues/342, there is still a problem of node-client sending data to nvim.exe in some scenarios with node-client 5.1.0. The problem described here is that after the https://github.com/neovim/node-client/issues/329 patch, when data is sent to nvim.exe, it does not crash nvim.exe anymore, however node.exe is terminated instead.
environment
neovim version (nightly from https://github.com/neovim/neovim/releases/):
node-client version: 5.1.0
Environment variable defined:
ALLOW_CONSOLE=1
(without it, it does not trigger)node: https://nodejs.org/dist/latest-v21.x/node-v21.7.1-x64.msi
nvim.exe receiving the data but not crashing
then breaking manually into debugger:
node.exe terminated