| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |\
| | |
| | | |
Miscounting of line in case of markdown `\ref` image
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we have:
```
The page
\aa2 Doxygen's Doxygen Documentation: <a href="https://codedocs.xyz/doxygen/doxygen/"><img src="https://codedocs.xyz/doxygen/doxygen.svg"/></a>\aa2
\aa3
\aa4  \aa4
\aa5
\aa9
```
we get the warnings:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:8: warning: Found unknown command '\aa4'
.../aa.md:9: warning: Found unknown command '\aa5'
.../aa.md:17: warning: Found unknown command '\aa9'
```
instead of the expected
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:5: warning: Found unknown command '\aa5'
.../aa.md:9: warning: Found unknown command '\aa9'
```
this is due to the fact that the markdown convertor adds some extra line wit `\n` instead of an internal line break `\ilinebr`.
|
| | |\ \
| | | |
| | | | |
Incomplete documentation in respect to hyphens for horizontal rulers
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
In case of a sequence of hyphens the documentation was incomplete.
(found during implementation of "Miscounting in markdown in case of a horizontal ruler", #8115)
|
| | |\ \ \
| | | | |
| | | | | |
Miscounting in markdown in case of a horizontal ruler.
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When having code like:
```
A horizonal ruler by means of underscores
\aa2
____
\aa4
A horizonal ruler by means of hyphens
\bb7
- ---
\bb9
A horizonal ruler by means of asterisks
\cc12
****
\cc14
```
we get wanungs like:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:5: warning: Found unknown command '\aa4'
.../aa.md:8: warning: Found unknown command '\bb7'
.../aa.md:11: warning: Found unknown command '\bb9'
.../aa.md:14: warning: Found unknown command '\cc12'
.../aa.md:17: warning: Found unknown command '\cc14'
```
instead of
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:4: warning: Found unknown command '\aa4'
.../aa.md:7: warning: Found unknown command '\bb7'
.../aa.md:9: warning: Found unknown command '\bb9'
.../aa.md:12: warning: Found unknown command '\cc12'
.../aa.md:14: warning: Found unknown command '\cc14'
```
This has been fixed.
|
| |\ \ \ \
| |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Changed DOT_MAX_FOLD to DOT_WRAP_THRESHOLD
- Improved documentation
- Applied DOT_WRAP_THRESHOLD to the whole string instead of individual
parts.
|
| | |\ \ \
|/ / / / |
|
| | |\ \ \ |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Removed the "Step x" text altogether.
- Removed some commented out code.
|
| | |\ \ \ \ \
|/ / / / / /
| | | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_doxywizard_layout
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some changes in respect to the layout of the doxywizard
- Vertical lineup of the "Step 1" "step 2" and "Step 3"
- "Condensed show configuration" by means of a checkbox an "Show configuration", checkbox including tooltip
- moving "Show HTML output" above the output.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Expand non-recursive preprocessor macros
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Small layout improvement in documentation of CLANG_DATABASE_PATH
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Small layout improvement in documentation of CLANG_DATABASE_PATH so some literal words are better shown.
|
| |/ / / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- Tooltips are now collected per file instead of globally
- Source reference lists now use STL containers
|
| | |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | | |
namespace without class (part 2)
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Confusing message for extension mapping for extension with starting dot.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When having the settings:
```
EXTENSION_MAPPING = .h=C++ \
.inl=C++
```
we get the, confusing, message with 2 dots:
```
Adding custom extension mapping: ..h will be treated as language c++
Adding custom extension mapping: ..inl will be treated as language c++
```
instead of
```
```
this has been corrected and made inline with the error in case of a non-supported language.
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
classes to appear in the class hierarchy.
|
| | |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | | |
namespace without class
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Miscounting in case of markdown links
|
| | | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
When we have simple input files like:
```
Chrome's trace viewer (Catapult) following the
[instructions](
https://chromium.googlesource.com/catapult/+/refs/heads/master/tracing/docs/embedding-trace-viewer.md). This directory contains
the helper files to embed Chrome's trace viewer.
The current resources were generated/copied from
[`Catapult@9508452e18f130c98499cb4c4f1e1efaedee8962`
](
https://chromium.googlesource.com/catapult/+/9508452e18f130c98499cb4c4f1e1efaedee8962).
\aa11
```
or
```
Add new exported module Text.Pandoc.Writers.AnnotatedTable [API change]
(#6655, Christian Despres). This module (which should generally
\bb3
```
one gets (in the current master version, a5ac10888f6c0b0fc00678f67aa49036b33aa4cf):
```
.../aa.md:8: warning: Found unknown command '\aa11'
.../bb.md:3: warning: Found unknown command '\bb4'
```
instead of
```
.../aa.md:11: warning: Found unknown command '\aa11'
.../bb.md:4: warning: Found unknown command '\bb4'
```
this is due to the fact that the newlines inside the links are not taken into consideration during the conversion.
We can add the extra newlines but have to do this inside the `<...>` as than they are handled correctly later on:
- when adding them before the `<` doxygen sees a newline and will start a new paragraph starting with the link instead of keeping it in its place.
- when adding them after the `>` we can get a warning about `warning: End of list marker found without any preceding list items` when after the closing `)` of the link there is directly a `.`
|
| | |\ \ \ \ \ \ \
| | |_|/ / / / /
| |/| | | | | | |
Miscounting in respect to lists in markdown
|
| | | |/ / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
When having examples like:
```
Steps
1. \aa2
2. \aa3
3. \aa4
\aa5
```
and
```
Steps
- \bb2
- \bb3
- \bb4
\aa5
```
we get warnings like:
```
.../aa_list.md:3: warning: Found unknown command '\aa2'
.../aa_list.md:4: warning: Found unknown command '\aa3'
.../aa_list.md:5: warning: Found unknown command '\aa4'
.../aa_list.md:6: warning: Found unknown command '\aa5'
.../bb_list.md:3: warning: Found unknown command '\bb2'
.../bb_list.md:4: warning: Found unknown command '\bb3'
.../bb_list.md:5: warning: Found unknown command '\bb4'
.../bb_list.md:6: warning: Found unknown command '\aa5'
```
instead off:
```
.../aa_list.md:2: warning: Found unknown command '\aa2'
.../aa_list.md:3: warning: Found unknown command '\aa3'
.../aa_list.md:4: warning: Found unknown command '\aa4'
.../aa_list.md:5: warning: Found unknown command '\aa5'
.../bb_list.md:2: warning: Found unknown command '\bb2'
.../bb_list.md:3: warning: Found unknown command '\bb3'
.../bb_list.md:4: warning: Found unknown command '\bb4'
.../bb_list.md:5: warning: Found unknown command '\aa5'
```
this is due to the fact that there is a line le counting. In case of REJECT no lineCount should be performed and otherwise just once.
|
| |/ / / / / / |
|
| |\ \ \ \ \ \ |
|
| | |\ \ \ \ \ \
| | |/ / / / /
| |/| | | | | |
issue #8105 How do add (multiple files without extension) directory in INPUT field of doxygen configuration file
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
field of doxygen configuration file
Small explanation added as it is not clear what to use in case of `no_extension` in `FILE_PATTERNS`
|
| |/ / / / /
| | | | |
| | | | |
| | | | | |
function leads to documentation error
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Warning about duplicate figure numbers in LaTeX
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In the log file of the generated doxygen manual we see warnings like:
```
pdfTeX warning (ext4): destination with the same identifier (name{figure.22.1})
has been already used, duplicate ignored
\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
```
(this pull request was also triggered by: https://stackoverflow.com/questions/64328597/pdftex-warning-saying-about-duplicate-figures)
The solution is found by means of: https://tex.stackexchange.com/questions/566677/multiple-use-of-figure-number-ext4-warning/ in short:
> The hyperref package patches \caption so \H@refstepcounter is used instead of \refstepcounter.
The definition isn't necessary in `manual.sty` as the `doxygen_manual.tex` includes `doxygen.sty`
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
issue #8093 Some URLs in fresh/updated Doxyfile are split over two lines
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Created an explicit split of the line before the http address so the URL will start on a new line in the doxygen configuration file and won't be split anymore (unless the total length of the URL will be longer than 78 characters but this is in the doxygen settings not the case).
(The other formats: HTML, LateX and the help in the doxywizard give still the same output results).
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Compilation warnings in doxyparse
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In doxyparse.cpp we got some compilation warnings (Windows 64-bit compiler) like:
```
doxyparse.cpp(299): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
```
these have been eliminated.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Don't start dvips when latex fails for formulas
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
In case the latex process fails for formulas there is no reason to try to start a dvips process.
|
| |\ \ \ \ \ |
|
