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 767171 - ALIASES stop working after verbatim with formula and /** */
ALIASES stop working after verbatim with formula and /** */
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: documentation
1.8.11
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-06-02 16:15 UTC by Cartucho
Modified: 2016-09-05 13:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Image of the bug (19.99 KB, image/png)
2016-06-02 16:15 UTC, Cartucho
Details

Description Cartucho 2016-06-02 16:15:49 UTC
Created attachment 328980 [details]
Image of the bug

ALIASES stop working if after the following @verbatim in the (markdown.file)

@verbatim
/**

\f[  \f]

*/
@endverbatim


---------------------------------------------------------------------------

Better description:

https://docs.google.com/document/d/1fLcEnctIFOpGEZoGa5zpdvOTX0g0yxEuC2lZTHrYkqo/edit#

OR:

1) Make a file with the following text inside:

Description {#mainpage}
=======================

## TEST

Before verbatim

@helloworld

@verbatim
/**

\f[  \f]

*/
@endverbatim

After verbatim

@helloworld

2) doxygen -g config
3) sed -i 's/ALIASES                =/ALIASES                = "helloworld=Hello World"/' ./config
4) doxygen config
5) open up html/index.html and you get (screenshot)
Comment 1 albert 2016-06-05 08:02:40 UTC
I've just pushed a proposed patch to github (pull request 482).
Comment 2 albert 2016-06-29 08:52:51 UTC
Patch has been integrated in main branch of doxygen.
Comment 3 Dimitri van Heesch 2016-09-05 13:45:21 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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).