Skip to content
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

TOC (@tableofcontents) does not work on mainpage (Origin: bugzilla #671158) #4597

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

Comments

@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

On 2012-03-01 19:31:59 +0000, kael@crocobox.org wrote:

on a @mainpage, @TableofContents does not print anything.

On 2012-03-01 20:26:21 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2012-03-03 01:17:04 +0000, Jason C wrote:

*** Bug 671239 has been marked as a duplicate of this bug. ***

On 2012-03-05 23:18:48 +0000, Alexander wrote:

Do we know when this bug was introduced?
--ap

On 2012-03-05 23:22:48 +0000, Jason C wrote:

@TableofContents is a new feature in 1.8.0 so it would have been in some development version after 1.7.6 and before now.

On 2012-05-19 12:26:36 +0000, Dimitri van Heesch wrote:

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

On 2012-05-22 15:20:17 +0000, kael@crocobox.org wrote:

not fixed in 1.8.1

On 2012-05-22 19:01:10 +0000, Dimitri van Heesch wrote:

Are you sure you are using doxygen 1.8.1?

I tried with the following example, and it worked fine:

/** @mainpage

So can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?

On 2012-09-22 21:37:59 +0000, Tobias Mueller wrote:

Closing as we believe this is fixed. Please reopen if this is not the case. thanks!

@doxygen doxygen closed this as completed Jul 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant