New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown fenced code blocks not parsed properly in comment (Origin: bugzilla #759177) #5904

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component build for ---
Reported in version 1.8.10 on platform Other
Assigned to: Dimitri van Heesch

On 2015-12-08 13:38:33 +0000, authmillenon wrote:

In v1.8.10 (Arch Linux) when using fenced code blocks like this

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

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])).

On 2015-12-09 12:09:39 +0000, authmillenon wrote:

Just an update: doesn't have this problem either. Seems to be only 1.8.10 that can't handle fenced code right now.

On 2015-12-19 18:59:08 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2015-12-30 10:20:17 +0000, Dimitri van Heesch wrote:

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).

On 2016-01-04 13:40:40 +0000, authmillenon wrote:

Fix confirmed

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment