Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No output in console or repl windows #108

Closed
MonsieurTib opened this issue Jan 2, 2025 · 4 comments
Closed

No output in console or repl windows #108

MonsieurTib opened this issue Jan 2, 2025 · 4 comments

Comments

@MonsieurTib
Copy link

fmt.Println("test") does not produce any output in the console or REPL windows.
This workaround resolves the issue, but I wonder if there's a specific configuration I'm overlooking in nvim-dap-go.
@Hank-GF
Copy link

Hank-GF commented Jan 6, 2025

I think it might be related to the following PR:
mfussenegger/nvim-dap#1405 (comment)

@tyanxie
Copy link

tyanxie commented Jan 14, 2025

I see there is already a pull request #109 to fix it. It would be great if @leoluz could approve this pull request. Otherwise, we won’t be able to see the output without customizing dap_configurations.

@leoluz
Copy link
Owner

leoluz commented Jan 14, 2025

#109 is now merged. Please confirm the fix and feel free to reopen if the issue persists.

@leoluz leoluz closed this as completed Jan 14, 2025
@CruelAddict
Copy link

The fix works for stdout of plain go programs, but when I debug tests with require("dap-go").debug_test() stdout is missing. Tried it both with and without tests.verbose flag, still nothing.

CruelAddict added a commit to CruelAddict/nvim-dap-go that referenced this issue Jan 17, 2025
@CruelAddict
Add outputMode and customization to test config
ee8c690 
Recent changes in nvim-dap behavior required setting `outputMode =
"remote"` in debug configs for stdout to be visible in REPL (see
leoluz#108 for more info). The
problem is now fixed for test scenarios too.

`test_debug` now accepts a `custom_config` argument as a way for users
to get around similar problems.
@CruelAddict CruelAddict mentioned this issue Jan 17, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@leoluz @MonsieurTib @CruelAddict @tyanxie @Hank-GF