WSLUser

So I'm not sure what changed and perhaps the functionality wasn't intended to work but it did. So if it needs explicit support in the win32 code, then I think...

If you want to run python scripts remotely, then you'll need to use fabric. This will still require python to be installed on the Linux host. Also keep in mind...

That looks to be an issue with your PATH. Yes I'm using Python 3.8 from the Store, running a fabric task that also requires a password prompt due to use...

> When creating the VHD's I'll make sure that compression and encryption are both disabled on them. Shouldn't the more correct solution be to support compression/decompression and encryption/decryption like you...

You'll likely want to see the discussion at https://github.com/microsoft/terminal/issues/7718, which should help considerably in implementing this.

See https://github.com/microsoft/terminal/pull/1263 for DirectWrite.

These are based on VT `CSI` which I think win32-input-mode wouldn't provide (as that's specifically for win32, not VT applications). It's technically the same, but different audience. Some popular editors...

https://github.com/microsoft/terminal/pull/11264 also would reveal the need for this, if we want to do independent things from conhost (which you seemed to have wanted from the your reply to the comment...

I guess the best proposol would be to re-work the input mode so that the win32 input would convert to one of the 2 proposed keyboard protocols. Easier would be...

Yeah I'm thinking https://github.com/microsoft/terminal/pull/11384 would probably help make this easier to implement as well. Perhaps @j4james would be interested in adding this support.