Commands executed internally do not interrupt the integrated console command prompt #411
Comments
daviwil
added a commit
to daviwil/PowerShellEditorServices
that referenced
this issue
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 PowerShell#411.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is 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.
The text was updated successfully, but these errors were encountered: