Sorry for the double post, but Yeong had a few great ideas! The first that I will talk about is accessing OS vars. We can now access the OS vars (A through Theta) in Grammer. We can read the values and write to them by prefixing their names with the imaginary i [2nd][.] then the letter. For example:
3→iA
iB→C
That stores 3 to OS var A and then stores OS var B to Grammer var C. So now we can interact better with BASIC programs (especially since Grammer code can be used inside BASIC programs).

So that is pretty neat, yes? So now for the second part of the update: Using multiple conditionals. Before, if you wanted to test, say, if C=5 or Enter is being pressed, you needed to have part of the conditional outside of an if statement:
getKey=9
If +C=5
...
This was a pain if you needed to preserve Ans! So now we can do something like this, by adding in a space or a colon between conditions:
If getKey=9 +C=5
...
The " +" is like using an OR operation on the two conditions, by the way. Similarly, " *" is like using AND. Also, this is not limited to only two conditions or just If statements. This can be used for While and Repeat loops, too

What do you mean by token changes?

Ah, okay. Well, not yet. I just want to warn that the Line(' command isn't totally complete, though

Could you do filled shapes?

Grammer currently does this with rectangles (10 fill methods)
I plan to do this with circles, eventually, too.
Other polygons might be a tad more difficult

Thick lines?

Once I actually add in a line drawing routine, I can probably do this My main issue is that I try to do things optimally for speed. For example, with rectangles, there is a method to draw the outline of a rectangle and clear the inside. It doesn't draw two rectangles to do this because that could really slow down the routine. Instead, it is its own, completely different drawing method

Text outputted one letter at a time? (typewriter style)

This can be done and might be pretty neat My question is, should this be a mode or should a special symbol be used in the Text( command to tell it to type that way?

Particle effects?

Greyscale?

I don't plan to add in built in grayscale, but you can simulate it, still

Thanks for the suggestions!

Okay, I added that in, but I am not sure if this will be permanent... should it be? Here is a screenie as well as the Grammer version with the update...

EDIT: Also, I added a way to change the text display speed of this mode. Use Fix Text( followed by a number (smaller number=faster display)

That wasn't too difficult, that is why it was fast However, particle effects might be

Also, I added the /Text( as another option and I found an issue If you tried using Typewriter Textas well as displaying a number or displaying text at the last cursor position, it would not work. So, I fixed that
Now Text( has four operators

And I would also like to point out that the only "tricky" part to this was making tokens display one character at a time. Luckily, I use my own text display routine, so it wasn't impossible

So now I have a question: What modes should I add? For example, Text Inverse is one I can add. I plan to change modes using Fix, so for example, Fix 1 is text inverse, Fix 0 turns it off. Does anybody else have mode ideas?

How would that work? If it is what I think, I might have to work on a routine for that...

I think I can manage that... This will give something to do for a while