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
I'm not using it atm because I don't find it very nice, but this is a possibility in case we want to improve the workflow.
Note that the above is Windows only so this will need to be ported for macos or Linux.
also note that before neovim 5.1.0, the logs were actually inside vscode due to 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 writing them to a file.
The text was updated successfully, but these errors were encountered:
At the moment, to visualize the neovim log when debugging, we need to show the content of a file outside of vscode, for instance in the terminal.
There is a way to actually open a terminal automatically and visualize the logs directly in the terminal using the following:
.vscode\tasks.json
:I'm not using it atm because I don't find it very nice, but this is a possibility in case we want to improve the workflow.
Note that the above is Windows only so this will need to be ported for macos or Linux.
also note that before neovim 5.1.0, the logs were actually inside vscode due to 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 writing them to a file.
The text was updated successfully, but these errors were encountered: