summaryrefslogtreecommitdiffstats
path: root/examples
diff options
context:
space:
mode:
authoralbert-github <albert.tests@gmail.com>2021-05-11 08:29:10 (GMT)
committeralbert-github <albert.tests@gmail.com>2021-05-11 08:29:10 (GMT)
commit4ba3ff7849f4d3291cbbdca8ab0b6888fd549701 (patch)
treea4f131eb6995ab579d29054273d7f0e131fda86e /examples
parentcd998a7164e30cee896cccd190846b79ebb4355f (diff)
downloadDoxygen-4ba3ff7849f4d3291cbbdca8ab0b6888fd549701.zip
Doxygen-4ba3ff7849f4d3291cbbdca8ab0b6888fd549701.tar.gz
Doxygen-4ba3ff7849f4d3291cbbdca8ab0b6888fd549701.tar.bz2
Confusing debug output for markdown
When having debug output one expects to have an overview what goes into the markdown processor and comes out of it. For markdown this happens but there can be a small step in front of it (page handling) and than the input is confusing as some processing already took place. When having a file aa.md: ``` This is a .md file ``` we get with `doxygen -d markdown`: ``` ======== Markdown ========= ---- input ------- @page md_aa aa\ilinebr This is a .md file ---- output ----- @page md_aa aa\ilinebr This is a .md file ========= ``` whilst it would be less confusing when we have: ``` ======== Markdown ========= ---- input ------- This is a .md file ---- output ----- @page md_aa aa\ilinebr This is a .md file ========= ```
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions