Josh Goebel

There is also sublanguage support, but I don't think that's what we want to do.

I'd start with VERY small snippets and then make your new grammars work with them, then expand.. and keep iterating... like start with: ``` body { background: green; } ```...

And if you also did Stylus and Less side by side then you'd see how they were all working at once... and if you did all this in a PR...

List them all out, the other just makes future maintenance hard. This is what gzip is for (saving bytes)... But I'd do even further and list then in array form...

I don't mind being smart for certain individual attribute though, such as for border: `border-(left|right|top|bottom)-(style|radius|width)` etc... That might actually make it easier to see what is going on and doesn't...

If I was doing it I'd probably do a mix in an array: ``` PROPERTIES = [ [string], [string], [regex], ... ] ``` Then you could use regex to describe...

**Though I still debate if you need an actual list.** It seems you could just match `something:` as a property, no? CSS does just fine now without having any lists...

> In this case, non-existent properties are also formed. Properties that will never appear in CSS files anyways. And how much easier to maintain is that that writing out 100...

> The problem is the stylus. How so? All the examples I see still have properties ending in `:` Oh I see you can also write: ```stylus body color white...

> Unfortunately for Stylus, the list of html members also seems to be necessary I'm not sure this is true, but it MIGHT be. It's definitely easier if you have...