@voretaq7 Or if it's off by default and needs to be manually turned on with the html comment?

Indeed - it's been a long time since then, and a lot has changed. We're in agreement, then. Thanks for clarifying!

Can you clarify if your opinion has evolved since your answer on the Mac Mini question, or if you still feel that that would be off-topic?

@MarkHenderson Haha, thanks! Maybe next year.

I'd also be curious to find out what the tiebreaker is. And for what it's worth, you had my vote - a big pile of rep isn't everything, and the moderation experience on another SE site goes a long way.

What'd be nice is if there were some good coloring for some of the common config file types we see - XML coloring would catch the handful of XML configs, but it'd be really cool to see some good coloring on Puppet manifests, Apache configs, Cisco configs, etc. I wonder how much of a pain it'd be to add types?

@jscott The in-source override syntax doesn't work.

Supposedly it's completely disabled on meta (so your test shouldn't work) but can be enabled with those lang tags only on main - see Shog9's comment.. but it clearly doesn't work (see this answer, for instance).

Manual specification of the language, supposedly overriding the highlighting from the tags, doesn't work. See this answer, for instance; I specified <!-- language: lang-c --> at the top of the code block and it didn't do anything.