Fixing the build output appearance in vscode#8129
Merged
jhorvath merged 1 commit intoapache:masterfrom Jan 13, 2025
Merged
Conversation
Member
|
Is there a reason why Run/Debug/Test appears in a Debug window, which is somewhat mixed between NBLS console/debug output and user code I/O and not in something like "Execution" Output window ? |
c615560 to
3d25acc
Compare
Member
Author
We want to keep Run/Debug/Test in the Debug window. On the other hand there is no way to get the rest of the outputs (like builds) there is it uses only VScode's debugger infrastructure |
sdedic
approved these changes
Jan 13, 2025
Member
sdedic
left a comment
There was a problem hiding this comment.
OK, definitely an improvement. It would be great to investigate NBLS stdout vs. Run/Debug stdout separation in a future release. Thanks.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The output from
AbstractLspInputOutputProvideris now displayed in a new terminal in VSCode. However, if the terminal is closed after the build finishes, it does not reappear when the next build is started.I am addressing this issue by ensuring the terminal is recreated as needed. Additionally, I am modifying the logic so that the outputs for Run, Debug, and Test actions are written to the VSCode Debug Console, as they were previously.