| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |\ \ \ \ |
|
| | | | | | | |
|
| |\ \ \ \ \ \ |
|
| | |\ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Problem with links from search index files
|
| | | | |_|/ / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The format of the tag file has been slightly changed in the past so that the original HTML_FILE_EXTENSION was preserved by adding the HTML_FILE_EXTENSION to the items in the tag file.
This change has not been reflected in the search files like `files_0.js` resulting in lines like
```
['core_5fbigfloat_2eh_8971',['CORE_BigFloat.h',['../../Number_types/CORE__BigFloat_8h.html.html',1,'']]],
```
this has been corrected.
(Found in the CGAL code).
|
| | |\ \ \ \ \ \
| | |_|_|/ / /
| |/| | | | | |
More indicative warning for wrong nesting of sections
|
| | | |/ / / /
| | | | | |
| | | | | |
| | | | | | |
In case we have a "*section" outside the hierarchy it is useful also have the id of the misbehaving "*section" even though line numbers are given , they might be misleading.
|
| |/ / / / / |
|
| |/ / / / |
|
| | | | | |
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Correct handling of error / removed debug statement
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In the vhdldocgen:
- error should be handled in a doxygen consistent way (in this case with an err call)
- removed left over debug statment (found through #7528)
|
| | |\ \ \ \ \
| | | | | | |
| | | | | | | |
More accurate warning message.
|
| | | | |/ / /
| | |/| | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
in code like `this command @unkn` would give (whilst all information is present)
```
warning: Found unknown command '\unkn'
```
instead of
```
warning: Found unknown command '@unkn'
```
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
and other small fixes
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_791390
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | | |
- added possibility (and checks) for xml
- added missing case for class in docbook
|
| | |/ / /
|/| | | |
|
| | | | |
| | | |
| | | |
| | | | |
use explicit constructor' issue on some versions of gcc.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | | |
https://github.com/maddox11/doxygen into maddox11-fixed-parser-bugs-javacc705
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \ |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
English version
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
The writing of the "pipe" symbol was done at the wrong moment.
|
| |/ / / / |
|
| | | | | |
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When feeding doxygen with:
```
%!test <*33536>
%! [a, b, c] = strread ("1,,2", "%s%s%s", "delimiter", ",");
```
in a `.m` files doxygen crashes.
The code is seen as Objective-C code but in fact is Octave (Matlab) code and as such not supported / not understood by doxygen. This should not be fed into doxygen, but also should not crash doxygen.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Based on the question: https://stackoverflow.com/questions/59685012/doxygen-markdown-links-to-main-page-do-not-work?noredirect=1#comment105616212_59685012
The markdown mainpage has no anchor so it is not possible to link to it, added an anchor so it is consistent with other page commands.
|
| |/ / / / |
|
| |\ \ \ \
| | | | |
| | | | | |
Possibility to use gswin64c on Windows
|
| | | | | |
| | | | |
| | | | |
| | | | | |
include file was missing
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
On windows the 32 bit executable is called gswin32c, but for the 64-bit systems also a gswin64c exists.
The path is checked for the existing of these executables (with a preference for the 32 bit version).
|
| |\ \ \ \
| | | | |
| | | | | |
issue #7484 Error: /undefined in getenv
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The command `ps2epsi` also uses the `gs` command and this gives some problems with the gs9.50 version.
An alternative is the `eps2eps` command that doesn't have these problems with the gs9.50 version.
See also:
- #7290
- https://bugs.ghostscript.com/show_bug.cgi?id=702024
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Updated Swedish translation to match the latest version
|
| | |/ / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Consistency `\*only` and `\end*only` commands
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Not all possibilities in respect of `\*only` and `\end*only` commands were present which could lead to messages like:
```
.../aa.h:4: warning: reached end of comment while inside a \rtfonly block; check for missing \endrtfonly tag!
../.aa.h:4: warning: rtfonly section ended without end marker
.../aa.h:4: warning: rtfonly section ended without end marker
```
in case of a problem like:
```
/** \file
* \rtfonly
* RTF /* Nested */
* \endrtfonly
*/
```
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Remove unused rules
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
Remove some unused rules.
|
