<h1 dir="auto">Environment</h1>
<p dir="auto">Affected: any supported Windows 10, currently 18362.10022<br>
Windows Terminal preview 0.5.2762</p>
<p dir="auto">Any other software?<br>
nothing special</p>
<h1 dir="auto">Steps to reproduce</h1>
<p dir="auto">Open Windows Terminal<br>
type commands or text<br>
select the stuff with your mouse<br>
press enter key</p>

<h1 dir="auto">Expected behavior</h1>
<p dir="auto">This should copy the selection into clipboard just as usual with legacy cmd / powershell terminal</p>

<h1 dir="auto">Actual behavior</h1>
<p dir="auto">pressing enter key will issue the command as if there was no selection in progress</p>
<ul dir="auto">
<li>
<p dir="auto">Your Windows build number:  (Type <code class="notranslate">ver</code> at a Windows Command Prompt)<br>
Version 10.0.18305.1003</p>
</li>
<li>
<p dir="auto">What you're doing and what's happening: (Copy &amp; paste specific commands and their output, or include screen shots)<br>
When using Bash on Windows (WSL) with Ubuntu 18.04, sporadically when exiting Vim on a remote host via ssh, the console stops rendering new text. It doesn't happen all of the time, and it seems that re-entering vim, then exiting immediately solves the problem; no need to close &amp; restart the shell.</p>
</li>
</ul>
<p dir="auto">What I've seen is that the cursor appears to be in the correct place, and it blinks as usual. The cursor moves in response to key presses. Key presses are sent, as when I'm in this state, I can type 'vim' and vim properly starts and renders. While I'm in vim, everything works as expected. When I exit vim (for the second time), it usually resets and the console works properly again.</p>
<ul dir="auto">
<li>What's wrong / what should be happening instead:<br>
I would expect that after quitting Vim, that the console would behave as normal. i.e. key presses are properly echo'd, the prompt is rendered, etc.</li>
</ul>