Yes, that looks like a spaces code bug to me. None of the spaces code should be changing the parser unless "/spaces on" is used. But it looks like it is affecting the parser in some way even while disabled. Ouch. This is going to take some debugging.
Update: thankfully, this was due to a bug in a single line of code, as opposed to an issue with the implementation approach as a whole. Whew. I'll be releasing an updated beta shortly.
Last edited by Khaled; 10/10/26 05:14 PM.