VS Code eats alias-expand-line key combination in git bash

[dfoverdx]

Issue Type: Bug

1. Open up an integrated terminal targeting git bash
2. alias foo='echo hello world' enter
3. foo ctrl+alt+e
4. Notice nothing happens

This is not the case using Windows Terminal + git bash, nor with opening git bash directly in Windows. I have tried updating my .inputrc to set alias-expand-line to a different key input--one that I know works--to no avail. I have no keybindings set to ctrl+alt+e in my Keybindings. This also doesn't work if I disable the Allow chords setting.

VS Code version: Code - Insiders 1.54.0-insider (e590188, 2021-02-26T20:39:10.253Z)
OS version: Windows_NT x64 10.0.19042

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on protected_video_decode: enabled rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.88GB (4.30GB free)
Process Argv	--crash-reporter-id 007f9f10-c4ef-458b-a674-6faaf4393697
Screen Reader	no
VM	0%

Extensions: none

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30263608
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256198
vstry244:30244315
pythonvsdeb440:30224570
pythonvsded773:30223139
pythonvspyt875:30259475
pythonvsnew554:30265444
pythontb:30258533

[ArturoDent]

Possibly related #81268 and https://bugs.chromium.org/p/chromium/issues/detail?id=959110. Unfortunately, the Chrome issue was not completed.

Fir what is worth, Chrome on W10 gives me this report:

Both Edge and Firefox onW10 report this:

So some extra keydown events in chrome seems odd. Could that be the problem for Electron?

[ArturoDent]

Also see #68787 and the fixes mentioned there.

[bluefrog845]

I have the same issue on 1.56.2 when sending any Ctrl + alt + key to WSL. It works fine if I open a WSL terminal outside of vscode.

[Tyriar]

It's possible another program could be interfering like in #68787, but I believe ctrl+alt+e isn't encoded for VT-based terminals. Supporting a new win32 input mode in the terminal backend is tracked in #135127

/duplicate