01:53 <marcan> alyssa: that explains why macOS was spitting out cropped/shifted cursor surfaces at one point...

01:55 <marcan> it just moves the cursor within the surface instead of cropping it within the src rect

02:23 <alyssa> marcan: oh, yuck

02:23 <alyssa> TTBOMK there is no way to express that in existing KMS and I am not volunteering for that bikeshed.

06:49 <rkjnsn[m]> marcan: re pipcet's observation of not seeing the final message from the installer, I believe if one accidentally hits enter twice at the preceding "Press enter to continue." prompt, that input() call only consumes the first press, and the second is buffered by the terminal, causing the final input() call to return immediately before the user has read the message.

06:50 <rkjnsn[m]> I haven't tested that on the actual installer, but do I see that behavior if I do: python -c 'import time;print("Press enter to continue. (1)");input();print("Sleeping");time.sleep(5);print("Press enter to continue. (2)");input();print("Done!")'

06:51 <marcan> rkjnsn[m]: then his system would've rebooted after the startup volume window closed, *without* having to press enter once again

06:51 <marcan> his story was that he pressed enter and *then* his system shut down, but the message prior to the shutdown was not the "press enter to shutdown" message

06:51 <marcan> that does not follow

06:51 <marcan> I considered your scenario when trying to figure out what happened, but his story isn't consistent with it ;)

06:53 <marcan> he said the system didn't reboot after the startup volume thing was done, which is exactly what the installer does

06:53 <marcan> and right after that it prints the info about what to do after shutdown, and the "press enter to shutdown" message

06:54 <marcan> therefore, since the system didn't immediately shut down at that point but instead waited for user action, that *had* to have been that final message