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

Using `@page` to add title to Markdown file generates surplus empty page. (Origin: bugzilla #765692) #5991

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

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

On 2016-04-27 18:55:54 +0000, Christoph Lipka wrote:

When using the @page special command to add a title to a Markdown file, even if the command is used as the very first line of the file, a page titled according to the Markdown file's base name is still added to the documentation, with no "payload" content.

For example, given this Markdown file:

-----------------------------------foo.md begins---
@page mypage My Page Title

Something

Dunno.

Something else

Never mind.
-----------------------------------foo.md ends---

the documentation will contain a page titled "My Page Title" with all contents of foo.md inside, but also a perfectly useless empty page titled "foo".

On 2016-05-16 10:33:39 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2016-09-05 13:45:25 +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).

On 2016-09-05 13:56:57 +0000, Christoph Lipka wrote:

Confirming this as fixed; thanks!

@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