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 lists are improperly nested (Origin: bugzilla #675757) #4698

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.0 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-05-09 15:29:57 +0000, wrote:

Created attachment 213738
Sample files plus Doxyfile that demonstrate the bug.

Using markdown to generate lists improperly nests the 2nd - nth element in the list. For example, the following:

  • item 1
  • item 2
  • item 3
  • item 4

Gets rendered as:

  • item 1
    o item 2
    o item 3
    o item 4

Same for numbered lists. Also, a paragraph after a numbered list becomes the continuation of the last item in the list.

I have included three files as an attachment. One is plain text, one is a python file and the last is C. The plain text version doesn't have the improper nesting issue, but does have the improperly indented paragraph issue. The python and C files demonstrate both problems.

I've included a minimal Doxyfile as well.

On 2012-05-09 19:02:43 +0000, Dimitri van Heesch wrote:

This is mostly a duplicate of bug # 671023, except for the paragraph 5 indenting issue, which should be fixed in the next subversion update.

On 2012-05-19 12:27:01 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1. 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.

@doxygen doxygen closed this Jul 2, 2018

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