The token swap on u, v, and w that becomes appv, grp, and var is happening within text strings as well, causing garbled text to appear in displays.

Version 0.4.4

You shouldn't be using the u, v, and w tokens in strings, that's what the lowercase alpha option is for . The u, v, and w tokens are different than the lowercase letters u, v, and w, and they aren't designed to be used in strings because they don't have ASCII character equivalences.

yes, that's right... but you can save them to somewhere else on your calc, and then place them back when ure finished outputting your text. that would be less work than writing your own routine.

wait a minute! I have written a text output routine! I'm gonna post it in the routine topic when I've found it!

Since I only needed to display three types of characters at the very right edge, I just converted them to sprites and used that

Thanks though, and the custom sprite routine might help someone else.

And a really weird bug report:

I've used lots of nested If -Else-End statements before, but for some reason, one particular combination gave me an error. Apparently, it didn't count the number of Else/Ends right, because I could either delete the nested Else or the nested End and it would compile with no errors (even though if I deleted the End, it would have a mismatched number of Ends).

I'll post the code when I find it.

If you use your own interrupt or turn them off, then the MirageOS interrupt will not work. If they're getting turned off and you're doing neither of these, it's because some instructions turn off interrupts. They can be re-enabled with FnOn after those instructions.
* calcdude asks Quigibo to document how instructions affect interrupts. (More specifically which ones turn them on/off)

The dispgraph commands have an unfixable hardware bug that disables interrupts after a while when in im2.  You have to explicitly use an FnOn after dispgraph if you want custom interrupts to remain on.

Before it always reenabled them for you by default, but I took that off for the case where you might have a dispgraph inside of an interrupt routine.  If the interrupts were to turn on automatically when they weren't supposed to for even just one instruction (before you have a chance to add the fnOff at the end) then horrible things can happen.

It seems to stop working after a while with just a simple display loop (with a counter going up of course.)

But I dont use dispgraph, I use output(
0->A
Repeat getkey(15)
output(0,0,A>Dec
A+1->A
End

And that sometimes disables after a while

You mean Mirage's interrupts don't work anymore? If so,

* calcdude asks Quigibo to document how instructions affect interrupts. (More specifically which ones turn them on/off)

^ seconded.