| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| | |
Documentation correction for CASE_SENSE_NAMES
|
| | |
| |
| | |
added missing "be"
|
| | |
| |
| | |
Did rephrasing things a bit.
|
| | |
| |
| |
| |
| | |
In issue #8129 the problem of using different case of filenames was addressed, though in the documentation it was not clear what this meant for input files.
This has been corrected (the underlying problem has been handled with different other commits a.o. 2b5a4541fb6f806c02a1f6e65a1ff2610f29751f ).
|
| |\ \
| | |
| | | |
64-bit Windows compiler warnings doctokinizer.l
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removing compiler warnings like:
```
.../src/doctokenizer.l(101): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
.../src/doctokenizer.l(844): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data
...
```
(analogous as done in e.g. `commentscan.l`)
|
| | |/
|/| |
|
| | |
| |
| |
| | |
iterators
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\ |
|
| | |\
| | |
| | | |
issue #8144 Problem with `\\` at end of an ALIASES in the configuration file
|
| | | |
| | |
| | |
| | |
| | | |
In principle a configuration file should not know anything about the doxygen commands, but the handling of the escaped `\` and `@` are an exception of this rule (especially in `ALIASES`).
The mentioned escaped characters were not handled properly.
|
| |/ / |
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_aliases_cmd
|
| | |
| |
| |
| |
| |
| | |
When we have an command like `\\`, `\@`, `@@` or `@\`in ALIASES this should not disturb the recognition of the replacement strings like `\2`, so e.g. `\\2` should not be replaced by `\y` but remain `\\2` (assuming the `\2` is linked to `y` in an ALIASES).
This issue was found after #8137 had been fixed and was already present in older versions as well.
|
| |/ |
|
| |
|
|
| |
As indicated in the issue the proposed fix fixes OP's problem (according to his initial tests) as well as the problem in the CGAL documentation.
|
| |\
| |
| | |
issue #8130 Markdown relative links - not working for other folders
|
| | |
| |
| |
| | |
Always convert links to absolute path even when path exists
|
| |\ \
| | |
| | | |
Remove double usepackage / RequirePackage from LaTeX
|
| | | |
| | |
| | |
| | | |
Remove double usepackage / RequirePackage from LaTeX initialization files (but keen multirow / multicol together)
|
| |\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_8137
|
| | |/ /
| | |
| | |
| | | |
In case the character directly following the number of a substitution marker is a backslash search directly a new substitution pattern
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
- Main goal was to avoid use of global state.
|
| |\ \ \
| | | |
| | | | |
issue #8127 Java: xml output of preformatted (`<pre>`) block adds para-block for blank lines (hindering certain manual parsing)
|
| | | |/
| |/|
| | |
| | |
| | |
| | | |
for blank lines (hindering certain manual parsing)
Don't terminate a paragraph and remove the whitespace when inside a pre block, but output the blanks.
|
| |/ /
| |
| |
| | |
see to it that the `\ilinebr` cannot be seen as part of the file name (backslashes can be present as path especially in case of windows).
|
| |\ \
| | |
| | | |
Redundant / incorrect required version of cmake
|
| | | |
| | |
| | |
| | | |
In the clang part the required version for cmake was 3.1 though in the general part (on the main directory) already version 3.3. was required.
|
| |\ \ \
| | | |
| | | | |
Miscounting lines with markdown backtick section
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we have a program like:
```
# test
~~~
npm
~~~
\aa5
~~~
npm ~~~
\aa8
```
we get the warnings like:
```
.../aa.md:6: warning: Found unknown command '\aa5'
.../aa.md:10: warning: Found unknown command '\aa8'
```
instead of:
```
.../aa.md:5: warning: Found unknown command '\aa5'
.../aa.md:8: warning: Found unknown command '\aa8'
```
This has been corrected.
Note: in the example tildes are used so the backticks show up in the github issue as well.
|
| |\ \ \
| | | |
| | | | |
Remove warnings from lexers
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove warnings (Windows 64 bit compilation) like:
```
warning C4267: '+=': conversion from 'size_t' to 'int', possible loss of data
```
from the different lexers by making use of more consistent data types.
|
| |\ \ \
| | | |
| | | | |
Miscounting lines with markdown table
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we have a program like:
```
# Test1
| \aa3 |
| ---- |
| \aa5 |
\aa6
```
we get the warnings like:
```
.../cc.md:3: warning: Found unknown command '\aa3'
.../cc.md:4: warning: Found unknown command '\aa5'
.../cc.md:6: warning: Found unknown command '\aa6'
```
instead of:
```
.../cc.md:4: warning: Found unknown command '\aa3'
.../cc.md:5: warning: Found unknown command '\aa5'
.../cc.md:6: warning: Found unknown command '\aa6'
```
The external counting was correct, not the internal counting.
This has been corrected.
|
| |\ \ \
| |_|/
|/| | |
Miscounting lines with markdown blockquote
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When we have a program like:
```
# test
\aa2
> \aa3
\aa4
```
we get the warnings like:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:4: warning: Found unknown command '\aa3'
.../aa.md:6: warning: Found unknown command '\aa4'
```
instead of:
```
.../aa.md:2: warning: Found unknown command '\aa2'
.../aa.md:3: warning: Found unknown command '\aa3'
.../aa.md:4: warning: Found unknown command '\aa4'
```
This has been corrected.
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| |\ \ \
| |/ /
|/| /
| |/ |
|
