New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exclusion of a new line at the end of source code file causing nesting of HTML code for function documentation (Origin: bugzilla #763720) #5970

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.11 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2016-03-15 21:55:16 +0000, wrote:

Created attachment 324050
Contains example source files, doxygen template, and screenshots of output.

When I have a header and source code file such as example.h and example.c and I don't leave a new line at the end of example.c, the HTML documentation for example.h and example.c nests every function after the first into the first function div. See the attached files for example code and screenshots.

On 2016-03-17 19:04:28 +0000, albert wrote:

Problem is hard to spot in the images but for the function sum_array the box around the code does not end after the code but continues when there is no newline at the end of the function.

I've just pushed a proposed patch to github (pull request 459)

On 2016-03-19 12:58:55 +0000, albert wrote:

Code has been integrated in doxygen master branch on github

On 2016-09-05 13:46:39 +0000, Dimitri van Heesch wrote:

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).

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment