There's grep -vE '0.*1|1.*[02]|2.*[13]|3...., and it looks like the asterisks, trigger italicizing, but surely they shouldn't do that in a code block?

@ilkkachu Amusing. I believe highlight.js is to blame, as explained here: meta.stackexchange.com/a/355375/410681

I.e. if a language for code highlighting is not specified and the question's tags tell the highlighting library to use lang-default, highlight.js starts guessing the language of each code block; and in that case it believes it's markdown.

Though I don't know how to check what language(s?) a question's tags resolve to, so I can't be sure.

@fra-san it's listed on the info page for a tag

but all the blocks in that answer are different, wrong, languages, not from the tags anyway

grep -> Markdown / perl -> Dart / sed -> Perl

and the edit preview doesn't show italics :/

@MichaelHomer Thank you. I was looking at tags that apparently don't have one, so I didn't see it's there.

e.g. right at the bottom of the perl info page, "Code language: lang-perl"

all completely wrong anyway. I have no idea how autodetection comes up with those answers

for some reason, it thinks the one that looks like line noise is Perl.

@AndrasDeak It does for me. But only if I actually change something and wait a few seconds.

Ah

so code fence + bash can fix it

ok thanks @fra-san and @MichaelHomer. Let's take this to meta: unix.meta.stackexchange.com/questions/5725/…