Skip to content

Conversation

@mfussenegger
Copy link
Owner

@mfussenegger mfussenegger commented Dec 23, 2024

Note that delve users will need to set outputMode = "remote", in their configurations to continue seeing the output of print statements in the repl. See #1407 (reply in thread)

@mfussenegger mfussenegger force-pushed the logging branch 2 times, most recently from 2124ae2 to e81fa79 Compare December 23, 2024 22:25
@mfussenegger mfussenegger changed the title Log stderr of adapters to dedicated files Log stderr of adapters to dedicated files; improve spawn error messages Dec 23, 2024
@mfussenegger mfussenegger marked this pull request as ready for review December 23, 2024 23:27
@mfussenegger mfussenegger merged commit 3b79616 into master Dec 24, 2024
16 checks passed
@mfussenegger mfussenegger deleted the logging branch December 24, 2024 10:40
leoluz pushed a commit to leoluz/nvim-dap-go that referenced this pull request Jan 14, 2025
nvim-dap had a change to log stdout/stderr of debug adapters to log
files instead of redirecting it to the repl.
(See mfussenegger/nvim-dap#1405)

delve by default outputs print statements on stdout instead of using
output events, which means they're no longer visible.

Setting `outputMode = "remote"` in a configuration causes delve to use
output events, which nvim-dap shows in the repl

See also mfussenegger/nvim-dap#1407
@mthnglac
Copy link

Is this still an issue? Currently, I'm debugging ruby code with ruby_lsp, and the DAP console is still empty.
cc: @mfussenegger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants