The reason there is an explicit test button is that, as some language grammar hackers will know, it is possible to create infinite (zero-width matching) cycles in the language grammar, which will make TextMate’s parser freeze (when using that grammar) -- so “live” editing of grammars is currently a bad idea (since an intermediate state could trigger the problem). The parser used for 2.0 will not have this problem, and so there is no real need to not apply the changes immediately.
I am aware, that this is very bad. I had underestimated the power of some of these regular expressions. The reason, why it takes me so long, to fix this for the txp Grammar, is that a couple of other things are wrong as well. So for me as a non-programmer the approach is the following: I regenerated the core-modules of the language, and currently test them one by one,when everything works I put everything together using snippets and macros in plist.scope. I am not getting any errors anymore right now, but it is going to take me some time, as there is a lot of testing involved.
regards, marios
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate