I was poking around, and I didn't really see anything that had syntax highlighting for Axe, so I made one for Gedit for fun.  This isn't really anything spectacular, but it was a good excuse for me to practice my regex skills

Add the file to the appropriate directory, and if your text file ends in .axe or if you select 'Axe Parser' from the Menubar ([View] -> [Highlight Mode] -> [Sources]), the syntax highlighting should kick in.  The colors you get should depend on what theme you currently have.

I believe this should support TokensIDE-style syntax (although it's been a long time since I've looked at TokensIDE, so I don't know how well this actually complies).


For Linux, just copy axe.lang to '~/.local/share/gtksourceview-3.0/language-specs' (or '~/.local/share/gtksourceview-2.0/language-specs').

Windows is apparently 'C:\Program Files\gedit\share\gtksourceview-2.0\language-specs\' or 'C:\Program Files\gedit\share\gtksourceview-3.0\language-specs\' (althought I can't confirm).

I don't know about Macs, sorry.


Props go to Deep Thought for inspiring me to write this.

Cool Michael, looking neat!

Looks nice! Is there any possibility to make it into a .8xp file?

There isn't a plugin for Gedit, per se (although I could try writing one, I suppose), but you could try using Croquette, a collaborative project between me and ephan -- just drag your text file over the exe, and out pops an 8xp (although you'll still have to compile it)

Looks nice! Some suggestions: define conditionals and controls structures (If, While, sub, Goto, etc.) separately from commands (Pt-Change, flipV, Copy, etc.) and define constants (10, Pic2, L4, °V, etc.) separately from data ("HELLO", [283A73B3], Data(5, 2341^r), etc.) and variables (H, r3, etc.). That is the way I did it in BBify; it encourages users to understand the difference between these types, which is very important in Axe.

Those are good ideas, thanks!