That's a good point, i'll update the patch accordingly. And per our other thread on your article i'll ping others in #o about what options people would like to see customizable.

Seems more likely that someone would do a whole bunch at once rather than a trickle, and also to be encouraged to reduce churn and chance of conflicts in the "address space" (hey, it wasn't my idea to use numbers instead of language names).

I think the regexing is easier than you've made it on yourself. Why not un-indirect the MP_WP_CODEBLOCK_OPEN which isn't meaningfully customizable anyway, and shrink the first set of parens to include just the number (as I showed)? Then no need for substr and you get multi-digits for free.

I meant for it to only be 0-9 as I think adding support for eight more languages will take quite some time. I'm grabbing the matched index from the array that preg_match_all populates (#S1-L37), which currently depends on it being a single-digit number (though it could be updated to grab any length between [[).

> This nonetheless comes at the cost of having to fork the v-tree. It occurred to me this one might warrant a global setting in wp-config.php, since it really seems to be a matter of taste/theme.

I could see that, perhaps the entire options can be set in wp-config.php? See also my comment on your recent article.

> So my current filter is: [...]

This is a nice simplification, thanks!

> I don't quite follow, but how does this handle multiple sequential spaces [...] ?

e.g. previously with the pre tag wrapped around the table, copying:

line1
line2

and pasting it would yield:

line1

line2

Multiple sequential spaces are handled as you would want/expect them to be (i.e. maintained). The pre tag was superfluous because of td.content-column { white-space: pre-wrap; } in the CSS.

> i. This is now a regex pattern to include an encoded syntax index.

Do you mean for this to allow only one digit? You could use \[([0-9]+)\[ so the parens capture the number portion (then there's surely a preg function to get at it).

> ii. ... Feel free to set it how you like using this variable.

This nonetheless comes at the cost of having to fork the v-tree. It occurred to me this one might warrant a global setting in wp-config.php, since it really seems to be a matter of taste/theme.

> v. ... This was all I needed for this article:

The closing characters don't generally need escaping, since they have special meaning only after the corresponding opening one (and footnotes-within-footnotes wouldn't work anyway AFAIK). Single/double quotes only need it in the context of an attribute (i.e. <a href="evil-user-input-here">). So my current filter is:

sed 's/&/\&amp;/g; s/</\&lt;/g; s/((/(\&lpar;/g'

> vi. I changed this to a plain div because the pre tag wrapped around the other markup (which is probably a misuse of the pre tag in any case) would cause extra newlines to be added when copy/pasting from the snippet into a text file.

I don't quite follow, but how does this handle multiple sequential spaces (as might be significant e.g. in a regexp even if one fully adopts MP's space-indent ban)?

> vii. This little bit of CSS avoids selecting footnote markers and line numbers when copy/pasting text from a codeblock. Go ahead, try it out.

That's very shiny!