 I have a bit of a demo here on my progress on the grammars for a text mate in general, apparently, but this is specifically being packaged for Visual Studio Code. Just because I did critique the one Alessandro De Sol did and also critiqued GPS, both of which essentially presenting themselves as finished products that should do a much better job, still working on this. I've mostly got the .80c grammar working, which is considerably simpler because it's just the NAT configuration file. It's just a list of progmas. But it does... I got it working with a level of depth that I would expect out of a finished product. A few little things I got to finish up, but you can see that this depth is possible and that I'm also just not talking out my ass or slandering things that I'm saying this is in like this should be better because it can be better. So if we bring up the scope inspector, you can see that for this line it does mark the... literally the whole thing as a meta.pragma. But this part specifically is recognized as a keyword, which is appropriate because it is a keyword. This is also recognized as a directive because it is a directive. This is one of the known progmas. And of course, one of the nice things about going with that approach, we'll drop that down here, one of the nice things about going with that approach is that you can correctly highlight known progmas and also mark other progmas as incorrect. So like if we... well I don't have that working yet apparently. But oh yeah, because of the way I'm checking for it. Yeah, because right now I'm just doing where was it? Where was it? Yeah here. That just any word is the directive. In this specific case is the progma. So I'd want to update that with the actual list of known progmas because then it will be able to correctly mark a correct progma versus an incorrect progma. Which you want. The big point behind syntax highlighting is to help you identify and make sense of the code easier. And obviously a huge benefit is marking correct progmas versus incorrect progmas because you can basically treat them like keywords. Just keywords that should only appear in a specific location. That is, after a progma keyword. But then to go a little bit further you can see once we go into the parenthesis you see meta arguments. And I think I showed this earlier when I clicked on it. But that it also does recognize the semicolon at the end of this as a punctuation dot terminator. And the meta progmas and meta arguments both work on repeating lines. So that will eventually pave the way for things like, I can turn this off now, these the positional notation for one of the parameters or arguments of the progma. Being highlighted appropriately and not confused for the identical syntax but different semantics that aspects have. Because with an aspect this would be the aspect's name. Whereas with the progma this right before the arrow in both cases is not the progma's name, but is the parameter or arguments name. So yeah, I'll continue on this. When I get the dot ADC finished, like everything is identified. I'll publish a beta of these grammars. There's literally nothing in the GPR by the way. I'll do that last but this is just an empty file. I don't even think I have it marked in package.json as anything that exists. But all the stuff with the progmas in here can be directly copied over because they have the same grammar to the general add a grammar. And then I can build up the rest of the stuff. So, yeah. Better is coming. Just takes a while.