Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

13
  • 3
    I like being able to do this, but I’m not a fan of the syntax. If we could just mark the first codefence as “all-none” (or generally: “all-X”) and have it work the same, that would be a win. (Maybe give a warning for using the old syntax too.) Commented Jun 1, 2020 at 13:05
  • 41
    Yes, the <!-- language-all: lang-something --> syntax will continue to work. Same goes for inferring the syntax highlighting language from the tags attached to a question. Commented Jun 1, 2020 at 14:52
  • 8
    FWIW, SO is not necessarily representative WRT the use of this feature, as tag-based inference tends to work pretty well. Sites where tags are not (or cannot) be configured for this purpose may tend to make more use of this as a convenient way to turn on highlighting. Commented Jun 1, 2020 at 16:16
  • 2
    @Shog9 I've ran it across the other main-site databases for posts since 2017 and numbers are still low. But as this is confirmed to continue to work the whole point is moot. Commented Jun 1, 2020 at 17:02
  • 3
    Does ``` none work now? Commented Jun 2, 2020 at 0:46
  • 2
    @Michael-Where'sClayShirky it works for me, yes. At least on MSO and MSE. If it doesn't work for you, please share the site where you are trying that. Commented Jun 2, 2020 at 5:42
  • 2
    @HamVocke Yet in your post you mention "Moving forward, this won’t work anymore.". How should we interpret this? Commented Jun 2, 2020 at 7:49
  • 6
    @Mast declaring the language for a specific indented code block is going away. With CommonMark's fenced code block notation we've got a perfect, standards-compliant replacement. Setting the overall language either by inferring it from tags or by declaring a <!-- language-all --> is going to stay for now. A new syntax highlighter might require us to revisit this in the future. Commented Jun 2, 2020 at 8:00
  • 2
    @HamVocke Ah, so setting it for the entire post the old style is still supported while for separate code-blocks only the new style is. We can work with that. Commented Jun 2, 2020 at 8:05
  • FWIW, I think your numbers are a little off, I've personally added that tag to multiple questions/answers on Code-Review 1,2,3. Is the query missing that site? Commented Jun 2, 2020 at 15:25
  • 2
    @Greedo now fixed, edited, new screenshots and links to new queries, thanks for catching that! Commented Jun 2, 2020 at 16:55
  • Tables: Feature Preview: Table Support Commented Nov 27, 2020 at 8:00
  • @P.Mort.-forgotClayShirky_q are you challenging me? ;) Commented Nov 27, 2020 at 10:16