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

All pages except main page are inserted by \include instead of \input in generated LaTeX (Origin: bugzilla #615957) #3740

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.6.3 on platform Other
Assigned to: Dimitri van Heesch

On 2010-04-16 13:52:58 +0000, wrote:

Condition: GENERATE_LATEX set to YES and COMPACT_LATEX set to NO

When creating documentation pages using \page command, they are inserted into the main tex file using \include instead of \input.

This results in a page break after the chapter heading in all page chapter except the mainpage chapter.

Note: Modifying the \include command to not insert page break is not an option as this would affect unwanted parts of the documentation.

Add another option to use \input in this case without affecting the rest of the documentation
use \input always as this seems to be the most natural choice (why would one want the chapter heading on a separate page in only these cases?).

The latter suggestion would require changing latexgen.cpp:1080 from
if (compactLatex || first) t << "\input" ; else t << "\include";
t << "\input" ;
in 1.6.3 source.

On 2010-04-16 19:20:30 +0000, Dimitri van Heesch wrote:

Confirmed. I'll replace the \includes by \inputs.

On 2010-06-15 11:21:42 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.0. 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.

@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