Skip to content

issue #6779 Multiple use of section label warning for Setex-stype headers in markdown#6780

Merged
doxygen merged 1 commit intodoxygen:masterfrom
albert-github:feature/issue_6779
Jan 19, 2019
Merged

issue #6779 Multiple use of section label warning for Setex-stype headers in markdown#6780
doxygen merged 1 commit intodoxygen:masterfrom
albert-github:feature/issue_6779

Conversation

@albert-github
Copy link
Copy Markdown
Collaborator

Due to the move of the markdown code to another place the adding of the section info of section, subsection etc. would be attempted to add twice (first in markdown and later on again when translating the resulting 'section, \subsection commands. The adding should only take place when handling the (replaced) commands.

Removing the test in addSection won't work as in that case using twice a sectioning command with the same label would not be signaled anymore.

…ype headers in markdown

Due to the move of the markdown code to another place the adding of the section info of section, subsection etc. would be attempted to add twice (first in markdown and later on again when translating the resulting '`section`, `\subsection` commands. The adding should only take place when handling the (replaced) commands.

Removing the test in `addSection` won't work as in that case using twice a sectioning command with the same label would not be signaled anymore.
@gschorcht
Copy link
Copy Markdown

Tested. Works as expected.

@doxygen doxygen merged commit fa28a4a into doxygen:master Jan 19, 2019
@albert-github albert-github added the fixed but not released Bug is fixed in github, but still needs to make its way to an official release label Jan 19, 2019
@albert-github albert-github deleted the feature/issue_6779 branch January 19, 2019 09:46
@albert-github albert-github changed the title issue #6679 Multiple use of section label warning for Setex-stype headers in markdown issue #6779 Multiple use of section label warning for Setex-stype headers in markdown Jan 19, 2019
@doxygen doxygen removed the fixed but not released Bug is fixed in github, but still needs to make its way to an official release label Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants