After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759177 - Markdown fenced code blocks not parsed properly in comment
Markdown fenced code blocks not parsed properly in comment
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: build
1.8.10
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-12-08 13:38 UTC by authmillenon
Modified: 2016-01-05 20:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description authmillenon 2015-12-08 13:38:33 UTC 
In v1.8.10 (Arch Linux) when using fenced code blocks like this

<pre>
/**
 * @defgroup snafu SNAFU
 * @brief    foobar
 *
 * - example code
 *   ~~~~~~~~~~~~~ {.c}
 *   int func(void)
 *   {
 *       return 1;
 *   }
 *   ~~~~~~~~~~~~~
 * - text
 */
</pre>

Doxygen yields `warning: Invalid list item found` and does not parse the code block as such (in HTML everything is outputted including the `~`). In previous versions this was working (tested with v1.8.6 (Ubuntu 14.04 [trusty]) and 1.8.8 (Debian 8.2 [jessie])).
Comment 1 authmillenon 2015-12-09 12:09:39 UTC 
Just an update: 1.8.9.1 doesn't have this problem either. Seems to be only 1.8.10 that can't handle fenced code right now.
Comment 2 Dimitri van Heesch 2015-12-19 18:59:08 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2015-12-30 10:20:17 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information 
that you think can be relevant (preferably in the form of a self-contained example).
Comment 4 authmillenon 2016-01-04 13:40:40 UTC 
Fix confirmed