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
With #2331 we support visualising logs inside vscode by spawning a task that does tail -f logfile.
However, before neovim 5.1.0 (node-client npm package), the native logs (console.log) were actually inside vscode natively but there was a bug that were not redirecting them into the custom logging system. see neovim/node-client#329 (comment) so it may actually be possible to use vscode debug console alternatively to writing them to a file.
It might be worth investing this again to see if we can get it to work with recent node-client.
The text was updated successfully, but these errors were encountered:
With #2331 we support visualising logs inside vscode by spawning a task that does
tail -f logfile
.However, before neovim 5.1.0 (node-client npm package), the native logs (
console.log
) were actually inside vscode natively but there was a bug that were not redirecting them into the custom logging system. see neovim/node-client#329 (comment) so it may actually be possible to use vscode debug console alternatively to writing them to a file.It might be worth investing this again to see if we can get it to work with recent node-client.
The text was updated successfully, but these errors were encountered: