Unknown input AND output regression between v1/v2 conhost

[htcfreek]

Description of the new feature/enhancement

Please add a button or menu entry that people can open the old CMD window settings. Sometimes there are situations where you need to change them. For example to enable legacy conhost behavior.

Proposed technical implementation details (optional)

[zadjii-msft]

So, here's an interesting question - why would you like access to the v1 console host/? We've got a mind to deprecate that entirely.

I'd honestly think it weird to have a quick shortcut to the conhost propsheet inside the Terminal itself. They're two different apps, they should have separate settings IMO.

[htcfreek]

So, here's an interesting question - why would you like access to the v1 console host/? We've got a mind to deprecate that entirely.

I'd honestly think it weird to have a quick shortcut to the conhost propsheet inside the Terminal itself. They're two different apps, they should have separate settings IMO.

In case I have an old app that requires the "Use legacy console" setting to be enabled for cmd. (Or make the setting no sense when using WT?)

[DHowett]

Okay, given that we are actively working on removing the legacy console, can you please let us know what application that is and how it breaks with the built-in non-legacy Windows Console Host?

[htcfreek]

Okay, given that we are actively working on removing the legacy console, can you please let us know what application that is and how it breaks with the built-in non-legacy Windows Console Host?

@DHowett
I will ask my colleague if we can share some information with you tomorrow.

Would it be possible to send you a PM/Mail with further information if required?

[DHowett]

@htcfreek Yes please! My e-mail is on my GitHub profile.