In the new v0.2.2, it seems that "tall" mode for print rendering does not render the final row of pixels.
See in this shot the difference between "tall" and "wide"

Haven’t tried it in “non-inverse” mode yet.
Discovered by using Zep’s “pinball everything” example.

Thanks for the heads up @ChristopherD

That last one is actually an issue with automatic scrolling when the cursor is at the bottom of the screen. I was able to reproduce the same output, but it worked when running it from a blank screen with the cursor near the top.

I'm confused about the first one though -- I can't seem to reproduce it. Do you get the same result from a clean boot? (maybe there is some state kicking around that shouldn't be)

poke(0x5f58, 0x2f)
?" 1 2 3 \n "

Here's what I get:

Also, this shouldn't matter, but which opreating system are you running 0.2.2 on? And it's 0.2.2, not the release candidate (0.2.2.rc1)?

@zep I'll check which exact version I was running (I wasn't aware there were multiple); it was just whatever was available on the primary download link.

Running on Windows 10 when it occurred.

I believe I had a clean boot when it occurred, because I downloaded and installed it, ran it for the first time, and I think the first thing I tried was I copy-pasted your Appendix A "pinball everywhere" line of code
poke(0x5f58, 0x1 | 0x2 | 0x4 | 0x8 | 0x20 | 0x40) -- pinball everywhere

and immediately saw the issue. Running again without 0x40 made it more clear.

Just confirmed with v0.2.2 on my Mac what you have seen.
Couldn't get the first problem to reproduce. cls then re-run the print statement for the last example prints correctly.

It occurred on v0.2.2 (not rc1)

oh, ok -- I got it! Thanks for the extra details. They are both caused by the scrolling bug, and I was able to get the same results as your original post just by starting at a certain cursor position. I'll pencil a fix in for 0.2.2b

Fantastic!
And thank you for making such a wonderful product