Josh Goebel

It's also *obvious* at least to me that someone building a slightly more complex scheme would likely *start* with named variables... why? For the very same reason [variables were added...

The whole idea of a variable/constant is that I only have to change things in a single place - this eases maintenance and reduces mistakes (most developers should agree here,...

It'd be useful to get the major editor template maintainers involved in this discussion I think. I for one like the TextMate scope hierarchy used in many editors (though we...

I'm thinking for first pass we simplify as much as we can, remove tiers... so I'd lose `integer`, `boolean` and `constant` and replace them with `literal`... and same splitting hairs...

https://www.sublimetext.com/docs/scope_naming.html I'm leaning towards just saying we support TextMate scoping names and mapping over the 20 or so that explicitly correspond to an `baseXX` and then let people go wild...

> Tm scopes are not enough to capture the theme. Example: status bar, button color, etc. Good point, we'd likely create a custom `ui` scope for this... on that point...

>For terminal apps, ... background, foreground, cursor foreground/background, selection foreground/background Yes, we'd likely need a few custom scopes for terminals... one could probably look to a project like https://github.com/mbadolato/iTerm2-Color-Schemes and...

One problem is "unequal" themes... templates have to be able to expect to know what output colors are available.... so if say we added ANSI scopes like `term.ansi.bright_red` which do...

From another thread: `diff_added`, `diff_added_background` This seems obviously (the pairing) but then you quickly realize there would be all sorts of problems to doing this. What if an app doesn't...

For builders I think the changes would be pretty simple: - Simply allow/welcome the additional YAML keys - (we might consider name-spacing or nesting for the official ones) - enforce...