| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
INLINE_SIMPLE_STRUCTS=YES
|
| |
|
|
| |
same name
|
| |
|
|
| |
Based on https://github.com/gulrak/filesystem/issues/128
|
| |\ |
|
| | | |
|
| |/
|
|
|
| |
also made some changes to make the templated HTML output better match the
built-in output.
|
| |
|
|
|
|
|
|
|
| |
When DISABLE_INDEX=NO and HTML_DYNAMIC_MENUS=YES (both defaults) then
on screens with a width smaller than 768 pixels, the menu will collapse into a
bar with just a hamburger button and the search field.
Also the search result window now stays within the limited of the
screen.
|
| |\
| |
| | |
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
=========
```
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8541
|
| | | |
| | |
| | |
| | | |
A `::` at the end is not necessary, intenmtion was to use make explicitly, by ".*` that all subpackages were used but that is not necessary.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
Adding the default packages from "java.lang"
From the standard "The Java® Language, Specification, Java SE 16 Edition" ,Chapter 7, Packages and Modules:
> Code in a compilation unit automatically has access to all classes and interfaces
> declared in its package and also automatically imports all of the public classes and
> interfaces declared in the predefined package java.lang.
|
| | | |
|
| |\ \ |
|
| | |\ \
| | | |
| | | | |
issue #8552 Javadoc: strange issue with @verbatim ... @endverbatim
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Similar problems can occur with the `\startuml` and `msc` command.
```
/**
* @startuml
* {\f} @code
* @enduml
*/
```
- some further needed corrections (for lexcode)
- `\endvhdlflow` does not exist
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
The end condition of a block was not detected correctly. in `scanner.l` (and thus `lexscanner.l` too) either the second part was missing or the compete test was missing.
Furthermore some conditions weren't handled correctly / incomplete.
|
| |/ / / |
|
| |\ \ \ |
|
| | |\ \ \
| | | | |
| | | | | |
Extra settings for MathJax V3
|
| | | | | |
| | | | |
| | | | |
| | | | | |
For support of the `\eqref` command (used in CGAL) in MathJax V3 a small change has to be made (for a rationale see the discussion on https://groups.google.com/g/mathjax-users/c/oS0yQLb5BMk)
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
REJECT
When we have a very large "LONGSTRINBLOCK" (e.g. a very large documentation part or an encode executable in e.g. base64 encoding) , there are a lot of lines that have to be read at once, this is not really necessary they can be read sequentially (probably at the cost of some speed)
|
| |/ / / /
| | | |
| | | |
| | | | |
- Also updated GHC's filesystem.hpp to version v1.5.6
|
| | | | |
| | | |
| | | |
| | | | |
base compound not resolved under certain conditions (part 3)
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_predefined_space
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When having in the settings:
```
PREDEFINED += "HELP_DOT_SPACE( xs , ys , ... )=enum class xs { ys, __VA_ARGS__}"
```
we expect that the result is similar to when using a PREDEFINED setting:
```
#define LOC_SPACE( xs , ys , ... ) enum class xs { ys, __VA_ARGS__}
```
this is not the case especially due to the space after the last named argument.
We see that when we have:
```
LOC_SPACE(locSpace2, last);
```
we get
```
enum class locSpace2 { last }
```
and when having:
```
HELP_DOT_SPACE(dotSpace2, last);
```
we get:
```
HELP_DOT_SPACE (dotSpace2, last)
```
|
| |/ / / /
| | | |
| | | |
| | | | |
base compound not resolved under certain conditions (part 2)
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Empty class definition.
|
| | | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In e.g. the HTML output of the doxygen documentation, chapter about formulas we see:
```
<p class="">
```
this is a regressing due to commit:
```
Commit: bb89b8136ff835c8fbd9f313d58815c8f361dff9 [bb89b81]
Date: Thursday, March 4, 2021 9:14:49 PM
Refactoring: some cleanup and removed text direction logic
```
made test now so that no empty class can occur.
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Inconsistent behavior between unknown command and unknown html entity
|
| | | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When having:
```
/**
* an unknown command \unkn
*
* an unknown html entity \
*/
void fie();
```
we get the, correct, warnings:
```
warning: Found unknown command '\unkn'
warning: Unsupported symbol \ found
```
but contrary to ``unkn` the text for `\` is not echoed to the output.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- avoids a second regEx
- compute ds.substr part only once
- unify varArgs only and fixed+varArgs cases
|
| |\ \ \ \ \
| |/ / / /
|/| | | |
| | | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8542
|
| | | |_|/
| |/| |
| | | |
| | | | |
The variadic macro was not handled in case there were fixed arguments as well.
|
| | | | |
| | | |
| | | |
| | | | |
base compound not resolved under certain conditions
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | | |
Incorrect handling normal C comment in comment converter
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
In normal C-comment (i.e. `/*` without extra `*` of `!` etc.) doxygen commands should be ignored.
This was notr te case see e.g.:
```
const char * /* O - or @code NULL@ */
zipcXMLGetAttribute();
```
|
| | |/ / / /
| | | | |
| | | | |
| | | | | |
The opening bracket was "forgotten" when the sharp count > 0 (in this case 1). the closing bracket was later on added to the name so the opening bracket is also be added to the name.
|
| |/ / / / |
|
| | |_|/
|/| |
| | |
| | |
| | | |
For easier debugging one can do e.g. `{% msg %}value={{ variable }}{% endmsg %}`
to list the value of a variable also when it is a list or struct.
|
| | | | |
|
| |\ \ \
| | |/
| |/| |
|
| | |/
| |
| |
| | |
As a regression of #8509 formulas that start a new environment (`\f{`) were considered as inline formulas as teh inline test looked for a `\{` but should look for `\begin{`.
|
| |/ |
|
