Michael Niksa

Just a quick note as confirmation: The original bug in the API discrepancy has been fixed in the last handful of Windows Insiders builds. This was MSFT: 10187355. We then...

@rprichard Apologies. I should have specified more about how the test writes. For all writes, we're starting with a cleared out buffer (all set to space characters `0x20` and the...

> @zadjii-msft is an option to configure the "lineHeight" still something we'd be interested in including? If so, I'd be interested in having a go at implementing this :) >...

The problem we're having here is biasing toward a perfect pixel cell grid, where each piece of the grid has an integer number of pixels in both the X and...

Okay, so here's what I said during triage that the team told me to put here: - For the most part, we don't want to continue improving the `ReadConsoleOutput*` family...

Aha. That is interesting now to better understand the scenario. One of the troubles right now I'm having with the "passthrough" mode that I made during our fix-hack-learn week a...

> Yes, it's the same idea as those F2/F4/F7/F9 popups. > > Also, `TakeShapshot` / `PutSnapshot` / `DeleteSnapshot` relatively nicely fit into the existing API: > > ```c > //...

Yeah @j4james... I agree both on the efficiency and security points. That's why I'm excited to understand the scenario as a sort of "keep a backup for me, let me...

> @miniksa do we have an active megathread for ongoing character sizing issues? See also #6738 I don't think so. We keep flopping on this because I think these Emoji...

> Huh. Weird. This one must just get shrunk into oblivion with the stretching we're doing. @miniksa as an FYI of a bug I'm throwing on you for 2.0 ☺️...