add Settings option to always create a new Terminal instance when outputTo=terminal #126
Conversation
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
pd93
approved these changes
Apr 5, 2024
|
Awesome! 🤩 |
|
When this will be released in VSCode marketplace? |
1 similar comment
|
When this will be released in VSCode marketplace? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Hello y'all!
This PR addresses the most basic part of #124 and #125 by adding a Settings option to have
"outputTo": "terminal"always create a new Terminal instance. Since this requires a bit more work on the user's part to keep from creating a mess of Terminal windows this behavior defaults to false, ie: turned off.I will attempt a second PR that will add the Settings option to create Terminal windows that end their process once the Task has finished (and prompt with the
Press any key to closeVSCode uses)