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 673921 - Paragraph mistaken as code block in indented comment block
Paragraph mistaken as code block in indented comment block
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.0
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-04-11 16:55 UTC by thevinn
Modified: 2012-06-10 09:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Comment block that demonstrates the problem (1.54 KB, text/plain)
2012-04-11 16:55 UTC, thevinn
Details

Description thevinn 2012-04-11 16:55:44 UTC
Created attachment 211854 [details]
Comment block that demonstrates the problem

When processing with MARKDOWN_SUPPORT = YES, a paragraph can be mistaken for a code block if the entire comment block is indented 4 or more spaces to the right and there is an existing code block present with the use of @code / @endcode tags.

The provided example demonstrates the problem. The paragraph starting with "Parameters..." is taken to be a code block when it shouldn't.

Removing the @code / @endcode section, or outdenting the entire comment block to the left resolves the issue.
Comment 1 Dimitri van Heesch 2012-05-27 18:37:59 UTC
The problem is not only the @code ... @endcode block, but the comment style

   /** This text is at indent 1

       This text is at indent 7

    */

which is now passed to doxygen's markdown parser as

 This text is at indent 1

       This text is at indent 7


Making the second line a code block.

I'll change it such that in this case also the first line is seen at indent 7.
Comment 2 Dimitri van Heesch 2012-06-10 09:41:44 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1.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.