On Mon, 22 Jan 2018 at 18:48:39 -0500, Gabriel Filion wrote: > I'm wondering why that was removed without any means to bring it back.
Not deliberately. As far as I can tell, ikiwiki has never gone to any particular effort to either enable or disable fenced code blocks, so whatever Text::Markdown::Discount does by default, that's the rendering ikiwiki will get. > [Fenced code blocks were] activated by an option when ikiwiki was > calling discount, and > for some reason that option was removed. So all fenced code block > rendering was completely broken by that change. You seem very sure that this was caused by an ikiwiki change. Can you point to that change in ikiwiki.git? You're right that fenced code blocks are documented as being activated by the MKD_FENCEDCODE flag, but we've never passed that flag to Discount anyway, and they apparently worked in the past. That makes me wonder whether this was an incompatible change in the Discount library or in libtext-markdown-discount-perl, rather than in ikiwiki. Looking at https://anonscm.debian.org/cgit/collab-maint/discount.git/log/?id=refs/heads/upstream it seems fenced code blocks might have changed from "configured at compile time, on by default" to "configured at runtime, off by default" in version 2.2.0. I suspect you observed this bug after upgrading from Debian 8 'jessie' to Debian 9 'stretch'. Please could you try downgrading the libmarkdown2 library from stretch's version 2.2.2-1 to jessie's version 2.1.7-1, and see whether fenced code blocks come back? smcv
