Skip to content

Interrupt integrated console command prompt when commands are executed #412

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.

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

Merged
merged 3 commits into from
Apr 3, 2017

Conversation

daviwil
Copy link
Contributor

@daviwil daviwil commented Apr 3, 2017

This change fixes a general class of problems in the integrated console
experience where commands that were executed internally (like extension
commands or running Plaster templates) do not interrupt the command
prompt, causing future input to be written over previous output lines.

The fix is to have the command prompt be interrupted by any commands
which write output or errors to the host.

Fixes #411.

This change fixes a general class of problems in the integrated console
experience where commands that were executed internally (like extension
commands or running Plaster templates) do not interrupt the command
prompt, causing future input to be written over previous output lines.

The fix is to have the command prompt be interrupted by any commands
which write output or errors to the host.

Fixes PowerShell#411.
@daviwil daviwil added this to the 0.12.0 milestone Apr 3, 2017
daviwil added 2 commits April 2, 2017 17:17
This change fixes an issue where invoking a Plaster template from within
VS Code causes Plaster prompts to be handled incorrectly because the
command prompt has not been interrupted.  The fix is to request that the
command prompt be interrupted when Invoke-Plaster is called.

Fixes PowerShell/vscode-powershell#643.
This change fixes a couple of issues that appear when the user presses
Enter to accept default values of input or choice prompts.  This issue
appeared when running through the default New Project template that is
shipped with Plaster.

Fixes PowerShell/vscode-powershell#504.
@daviwil daviwil merged commit cfd4959 into PowerShell:develop Apr 3, 2017
@daviwil daviwil deleted the execution-options branch April 3, 2017 00:26
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.

2 participants