doxygen version: 1.8.15
Operating system: Ubuntu 18.04 LTS
Doxyfile: standard
Using Setext-style headers in markdown files throw the warning: multiple use of section label 'xyz' while adding section, (first occurrence: <file>, line <n>).
The problem seems to be that labels are first appended to the sorted dictionary
|
g_current->anchors->append(si); |
and are therefore already known when
addSection is called after that from
The problem occures in version 1.8.15 and the current master as well. It wasn't a problem in 1.8.14. I have used the simple test file together with the standard Doxyfile.
Main Page {#mainpage}
=========
Section 1 {#section1}
---------
Test text for section 1
Section 2 {#section2}
---------
Test text for section 2Maybe the problem is related to #6605, but the problem described there seems not to be related to markdown support. Furthermore, since he claims that the problem didn't occur in 1.8.6, it is not really clear whether his problem report is for 1.8.7 or any newer version. In version 1.8.7 there was a problem that led to the problem described here. Therefore, I open a new bug report since it is in current version an related to markdown support.
doxygen version: 1.8.15
Operating system: Ubuntu 18.04 LTS
Doxyfile: standard
Using Setext-style headers in markdown files throw the warning:
multiple use of section label 'xyz' while adding section, (first occurrence: <file>, line <n>).The problem seems to be that labels are first appended to the sorted dictionary
doxygen/src/markdown.cpp
Line 2303 in dc89ac0
and are therefore already known when
addSectionis called after that fromdoxygen/src/commentscan.l
Line 1780 in dc89ac0
The problem occures in version 1.8.15 and the current master as well. It wasn't a problem in 1.8.14. I have used the simple test file together with the standard
Doxyfile.Main Page {#mainpage} ========= Section 1 {#section1} --------- Test text for section 1 Section 2 {#section2} --------- Test text for section 2Maybe the problem is related to #6605, but the problem described there seems not to be related to markdown support. Furthermore, since he claims that the problem didn't occur in 1.8.6, it is not really clear whether his problem report is for 1.8.7 or any newer version. In version 1.8.7 there was a problem that led to the problem described here. Therefore, I open a new bug report since it is in current version an related to markdown support.