<h1 dir="auto">Environment</h1>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="Windows build number: 10.0.18362.175
Windows Terminal version (if applicable): 0.2.1715.0

Any other software? No"><pre lang="none" class="notranslate"><code class="notranslate">Windows build number: 10.0.18362.175
Windows Terminal version (if applicable): 0.2.1715.0

Any other software? No
</code></pre></div>
<h1 dir="auto">Steps to reproduce</h1>
<p dir="auto">Using a brazillian ABNT2 keyboard, open any terminal and type <code class="notranslate">right alt + Q</code>.</p>

<h1 dir="auto">Expected behavior</h1>

<p dir="auto">This should type <code class="notranslate">/</code> in any type of terminal.</p>
<h1 dir="auto">Actual behavior</h1>

<p dir="auto">When using <code class="notranslate">bash</code>, it deletes the rest of the typed line. When using <code class="notranslate">powershell</code> or <code class="notranslate">cmd</code>, it types <code class="notranslate">^_</code></p>
<p dir="auto"><strong>Your Windows build number:</strong><br>
10.0.18362.86</p>
<p dir="auto"><strong>What you're doing and what's happening:</strong><br>
Trying to enter the <code class="notranslate">@</code> sign on a Swedish keyboard in a PowerShell console using <code class="notranslate">Alt Gr</code> + <code class="notranslate">2</code>.<br>
See animated gif:</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/357872/57315225-7099c400-70f3-11e9-803f-4d60d11feef5.gif"><img src="https://user-images.githubusercontent.com/357872/57315225-7099c400-70f3-11e9-803f-4d60d11feef5.gif" alt="terminal" data-animated-image="" style="max-width: 100%;"></a></p>
<p dir="auto"><strong>What's wrong / what should be happening instead:</strong><br>
Windows terminal shows <code class="notranslate">digit-argument</code> instead of outputting the <code class="notranslate">@</code> sign as expected.</p>
<p dir="auto">It's possible this is a PEBKAC error somehow but the problem doesn't show up in the normal PowerShell console... 😓</p>