Well, an Axe tutorial would be nice indeed, but what you just said is IMO more like a description of every command, rather than a tutorial, which explains how to use the language and some programming aspects and stuff.

This sounds like a good idea! I am hoping to learn Axe and could really use some help!

Hopefully this is a group effort and not just me.
I will try to add one each day, is anyone willing to do the basics?

Here are the basics:
Numbers in Axe aren’t the nice as-big-as-you-want-with-decimals, rather they are an integer with a range of 0-255 for an 8 bit number or 0-35565 for a 16 bit.
If a number is greater than its max it will loop back to 0.
You can simulate negative numbers though. 255 can act as -1. For example if you add 1 and 255 it will loop back to 0 just like 1 + -1 = 0. This trick works for all numbers, -2 = 254…
In Axe (and a lot of other languages) variables don’t hold numbers, rather they hold a pointer.
A pointer is like a direction to a location. The variable bossHp would contain some number (you don’t need to know what it is) that points the place where the computer stores the number for the boss’s health.
However rather than think about what they are the letter variables (and a few others) act just the way you think they should. If you ask it to display the value of A it will tell you it’s value NOT its pointer.
The most important thing in Axe is lists or as I will call them, arrays. Arrays are just lists of 8 bit numbers (range 0-255). L1 is a pointer to an area of FREE RAM. Free ram is basically areas of memory that the calc uses for various reasons that the ordinary user can’t use. However in programs you can use them. Some areas contain information and using them could produce weird results, I will be using L1 which is actually named saveSScreen which contains no important information.
The first line of code is ALWAYS a period then the name of the program once it is compiled.
Here is how you use them (example code):
:.EXAMPLE
:5->{L1}
:Disp {L1} >Dec
:2 -> {L1+1}
:Disp {L1] >Dec
Once this is compiled and run it will display:
5
2
Okay… so what did I just do? You probably got the 5 and the 2 are the same ones displayed, but what are the {} and the +1 and L1?
L1 is the pointer to the area of memory I want to use, it tells the program where to store the data.
The {} tell the program that I want the value stored there, NOT the pointer.
Finally, the +1 means I want the 2nd item on the list, that way I am not overwriting the first value.
Now, if you didn’t get the correct result here are some reasons what could be wrong…
>Dec is one token it is found under the math menu.
Did you compile the program?
Did you run prgmEXAMPLE ?
Is there a period in front of EXAMPLE (in the program)?
You need to use the Asm( prgmCompliedProgramName) to run the compiled program.

Some things to remember…
The source code (the part you edit) and the executable (the part you run) are separate.
There is a limit on the size of all areas of free ram (nothing has unlimited memory) for L1 / saveSScreen is 712. If you try to modify {L1 + 1000} bad things will happen.
What are those bad things? Well, it will probably corrupt you RAM. What is that? You can tell if your RAM is corrupted if you go to the memory menu (I won’t spell out how to get there) and go to the 2nd option: “Mem Mgmt/Del” and scroll down. There will be a nice list of all your programs apps and appvars but if something is wrong you will notice some impossibly large entries. For example it might say that Y1 is 61592 bytes large (the total amount of ram is only about 24000) so, it can’t logically exist. The only way to fix it is, well… a RAM wipe. You need to archive everything important and reset you RAM. If you look back the weird files should be gone.
What to do if your calculator freezes: There isn’t really much you can do, your only option is to open the battery case and remove one of the batteries and put it back in. This will cause the calc to reset RAM. Note: you don’t get to archive your files so if they are in RAM they will be lost!
I recommend some kind of shell like Doors CS 7 as it lets you edit a program in archive and run programs without using the Asm( command as well as a LOT of other functions.
If your program doesn’t work as expected it probably isn’t Axe’s fault. I know I sometimes blame Axe in frustration. Look closer. I have never found a problem that was Axe’s fault. (Thanks Runner!)
Remember, all it takes is a bit of practice.
Check back later for some instructions on how to use some of the other commands.
Please post if you have any questions (or comments).
Don’t let the whole list of things that could go wrong discourage you, those are all of the major problems, and I haven’t really covered the basics yet of what Axe can do!

Really? I have never heard of it or come across it in all my searches for help.
I guess it is easier to start a new thread than try to revive an old one.
(just how old is it?)
My ultimate goal is to "compile" all of the tutorial and the command overviews into one document.

True, but dudeman313 asked me to teach him Axe and I might as well see how far I can get.
We am also working on a side-scrolling-no-story line-combat game and I could use some help.
(That is what Bog Sluzi is for)

Maybe I thought that if I asked for people to just write a short overview on a command that I would get some help 

If I view it w/ Google Chrome, I might get a mangled but somewhat understandable meaning...

EDIT:
Here's where I point out how clueless I am when it comes to code:
Where would I enter the code in that tutorial above? All Axe Parser does is compile
& stuff.