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 153364 - With DETAILS_AT_TOP=YES, doxygen needs a <br> after details and before #includes
With DETAILS_AT_TOP=YES, doxygen needs a <br> after details and before #includes
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.3.x
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks:
 
 
Reported: 2004-09-22 05:13 UTC by Matthias Klose
Modified: 2018-07-30 10:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Klose 2004-09-22 05:13:10 UTC
[forwarded from http://bugs.debian.org/264499]

When the doxygen configuration file has

DETAILS_AT_TOP = YES

it generates html for the files that does this:

Definition in file <a class="el"
href="mq-local_8c-source.html">mq-local.c</a>.<code>#include "mq.h"</code><br>

Which runs the #include text immediately after the preceding link to
the file's source code, and it is mostly rendered on the same line by
the browser (depending on window width).

A <br> or <p> tag (or some other way to separate the two sections) is
required after the link to the source code, and before the first
#include.
Comment 1 Thadeus Fleming 2017-07-10 16:21:38 UTC
This bug concerns an obsolete configuration option and can probably be closed.
Comment 2 André Klapper 2018-07-30 10:00:30 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!