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 726469 - Tilde sign in combination with <pre> and MARKDOWN_SUPPORT disabled
Tilde sign in combination with <pre> and MARKDOWN_SUPPORT disabled
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: build
1.8.6
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-03-16 17:42 UTC by albert
Modified: 2014-04-22 17:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description albert 2014-03-16 17:42:02 UTC
Based on the message by Timo Kunze (http://doxygen.10944.n7.nabble.com/Starting-with-1-8-4-I-get-a-blank-output-td6509.html)

When having the following input file with a standard configuration file:
/// \mainpage mp Main
///
/// <pre>
///      pre text
///      ~~~~
/// </pre>

The following error message is given (this is correct according to documentation paragraph: 5.2.3 Fenced Code Blocks, though not sure if this is correct when inside <pre>):
fence.cpp:7: warning: reached end of file while inside a (null) block!
The command that should end the block seems to be missing!

When disabling MARKDOWN_SUPPORT the error message is still present which is unexpected.
When also removing <pre> and </pre> no error message is given.

Looks like that when in <pre> is enabled there is an interaction with the fenced code block.
Comment 1 Dimitri van Heesch 2014-04-12 14:41:20 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2014-04-21 10:09:28 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).