You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As detailed in #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 #329 patch, when data is sent to nvim.exe, it does not crash nvim.exe anymore, however node.exe is terminated instead.
justinmk
changed the title
node.exe terminated when data is sent to nvim.exe
ALLOW_CONSOLE should write to stderr instead of stdout, to avoid breaking stdio RPC channel
Mar 26, 2024
justinmk
changed the title
ALLOW_CONSOLE should write to stderr instead of stdout, to avoid breaking stdio RPC channel
logging: ALLOW_CONSOLE should write to stderr instead of stdout, to avoid breaking stdio RPC channel
Oct 11, 2024
As detailed in #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 #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
The text was updated successfully, but these errors were encountered: