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 723299 - Last line of code block lost if it is only one character and there is no text afterward
Last line of code block lost if it is only one character and there is no text...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.6
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-01-30 16:25 UTC by Gary Aish
Modified: 2014-04-21 10:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Document with examples of failing case and working cases. (210 bytes, application/octet-stream)
2014-01-30 16:25 UTC, Gary Aish
Details

Description Gary Aish 2014-01-30 16:25:03 UTC
Created attachment 267659 [details]
Document with examples of failing case and working cases.

In a markdown style indented code block, the last line of the code block is lost if it contains only one character and there is no text after the code block before the end of the page.

For example, this source:

/*!
\page test Test

Some text.

    Line1
    A

*/

Results in a page like this (note that the "A" is not in the output):

   Test

   Some text.

   Line1


However, if you add an extra character to the last line, the last line of the code block is in the output. For example:

/*!
\page test1 Test1

Some text.

    Line1
    AB

*/

Results in a page like this:

    Test1

    Some text.

    Line1
    AB


Also, if there is some text after the code block, the last line of the code block is in the output. For example:

/*!
\page test2 Test2

Some text.

    Line1
    A

More text

*/

Results in a page like this:

    Test2

    Some text.

    Line1
    A

    More text
Comment 1 Dimitri van Heesch 2014-02-06 20:26:00 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2014-04-21 10:09:36 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.7. 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 (preferrably in the form of a self-contained example).