Dustin L. Howett

That's probably the result of identical code folding. That specific `produce` adapter with that set of arguments is likely to be highly common between all C++/WinRT implementation types in `Microsoft.UI.Xaml.dll`....

> which isn’t exposed to the Settings UI because why should we? Because that setting literally tracks where the profile came from. There is no meaningful change you can make...

> Is it possible for the terminal to know what (sub)process it is currently hosting? To an extent, yes :) We have it on the books to track what we're...

Won’t that destroy the prompt start and prompt end locations, which we use for some of our detection features? Or would we figure those out after the fact by checking...

The preview version of Terminal stores settings in a different place than the stable version, because they may be incompatible and refer to preview-only features. 1.19 is the current Stable...

That's definitely not expected. A build-to-build upgrade should always preserve your settings. I was confused because your bug title included the 1.19 **preview** version number, rather than the 1.19 **stable**...

_Holy s\*\*\*_!

@aleksey-hoffman we await your pull request! Thanks!

@aleksey-hoffman it’s just... it’s generally considered poor form to find a feature request and gesticulate wildly about how “easy” it would be or how the maintainers are ignoring a common...

@lhecker is this a request for a change, or a "i will sign off and we can fix it more later"?