Open
Description
Prerequisites
- I have written a descriptive issue title.I have searched all issues to ensure it has not already been requested.
Summary
Currently it seems output streams of the debugee are routed to stderr of the editor services. Is there a reason DAP OutputEvent are not being used for this?
Context:
mfussenegger/nvim-dap#1419 (reply in thread)
The DAP client for nvim recently started routing stderr of debug server to logfiles rather than showing it to users. This change on client side now prevents me from seeing the outputs streams of my debugee in neovim. Apparently most debug servers use OutputEvent to communicate output streams, so clients will be more likely to have support for this!
Proposed Design
Use OutputEvent to communicate the output streams rather than stderr.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
JustinGrote commentedon Feb 27, 2025
@Willem-J-an thanks for your submission! I imagine this is probably some legacy behavior as PSES predates DAP. I agree this is something we should at least support with an option, marking "Up for Grabs" and will shepherd PRs if someone gets to it before me.
JustinGrote commentedon Feb 27, 2025
After doing some initial investigation, I imagine it has something to do with this in the DAP spec:
Since PowerShell typically operates as a host, and there's some janky stuff we need to do when hitting a debug to be able to get PSCallStack on remote powershell sessions, it would be my guess this is the reason. That being said, I'm sure we can figure something out where, as long as the session is local, to have an alternate output option,