| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | | |
|
| |/
|
|
| |
Regression on #7050 / #7053 (Physical newlines (^^) not working in group names and without spaces in 1.8.15), in case the current name was explicitly set to mainpage it was still overwritten.
|
| | |
|
| |\
| |
| | |
Bug 164073 - There should be a dummy tag that Doxygen ignores
|
| | |
| |
| |
| | |
Introduced the `\noop` command to ignore text till end of the line.
|
| | |
| |
| |
| | |
after @ref (try 2)
|
| | |
| |
| |
| | |
after @ref
|
| |/
|
|
|
| |
Create a consistent way to display the state mnemonics of the different scanners (analogous to the fortranscanner.l)
Use an automatic procedure to generate the routine with the translation of the states to a string.
|
| |\
| |
| |
| | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_endblock_msg
|
| | |
| |
| |
| | |
Consistency
|
| | | |
|
| |\ \
| | |
| | |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/bug_doc_cont
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case we have a documentation block that is interrupted the following part is directly appended to it without an appropriate newline and results, in this case, in messages like:
```
aa.c:13: warning: Illegal command @verbatim as part of a title section
aa.c:15: warning: unexpected command endverbatim
bb.f:13: warning: Illegal command @verbatim as part of a title section
bb.f:15: warning: unexpected command endverbatim
```
We need a solution at 2 places due to the reset of of `OutputBrief` to `OutputDoc` in `setOutput`
The original problem results from the "The R Project for Statistical Computing" version 3.6.1 in the Fortran part.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Regression on #7122 (and #7115 / #7116).
When having multiple consecutive `\name` sections the warning "unbalanced grouping commands" appears
Analogous to the open command also the close command needs an implicit argument.
|
| |\ \ \
| | | |
| | | |
| | | | |
https://github.com/albert-github/doxygen into albert-github-feature/regr_7105_2
|
| | |/ /
| | |
| | |
| | | |
In case of the `\name` command it is possible that a group is opened, but this group is not closed (for the `\name`), so the counting should not increase.
|
| |\ \ \
| | | |
| | | |
| | | | |
into albert-github-feature/regr_7105
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case of an extra closing we should not count this closing as otherwise sequences like:
```
@}
...
@{
...
@}
```
will give a warning at both `@}` statements and not just at the first (second one has an opening statement_.
|
| |\ \ \
| | | |
| | | | |
End comment marker in \code section.
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we have an end comment in a `\code` segment in a section we can get a message like:
```
warning: found */ without matching /* while inside a \code block! Perhaps a missing \endcode?
```
in the similar situation in a `\verbatim` section this message is not given. Switching from `\code` to `\verbatim` is not an option here as in that case other "commands" can lead to problems like in a code like `$string =~ s/^\s*//;`
In this patch the start `/*` and end `*/` comment markers for `\code` and `\verbatim` are completely ignored.
|
| | |/
|/|
| |
| | |
Signed-off-by: Adrian Negreanu <groleo@gmail.com>
|
| | |
| |
| |
| |
| |
| |
| |
| | |
group markers "@{"..."@}"
There are 2 sorts of grouping, with and without preceding group command.
In case og a preceding group command a warning was already issued, but without preceding group this was not done
Also corrected wrong order of `\{` `\}` commands, i.e, when we see more closing before opening commands.
|
| |\ \
| | |
| | | |
Missing brief descriptions with `\defgroup`
|
| | | |
| | |
| | |
| | |
| | | |
Due to the fact that issue #6945 ended a brief description, all following was put into the detailed description (unless explicit \brief was used). The `\defgroup` should end the current brief description, but first line of the `\defgroup` should be seen as a new brief description.
Problem can be seen with in the doxygen documentation in the example in the Grouping part and also with #7053 a small example is given in the comment.
|
| |\ \ \
| |/ /
|/| |
| | | |
https://github.com/albert-github/doxygen into albert-github-feature/issue_7050
|
| |/ /
| |
| |
| |
| |
| |
| | |
spaces in 1.8.15
Handling of `\_linebr` with defgroup and also with the `\page` command.
Adding a missing linecount.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
In case we have something like (taken loosely from issue #4554):
```
- \subpage id_201201031218 \copydoc id_201201031218
```
this would be translated into:
```
- @subpage id_201201031218\copydetails id_201201031218]
```
and subsequently the first word of the `\copydetails` part is placed directly to the `id_201201031218` resulting in an unknown id like `id_201201031218this`
(This actual case it doesn't make much sense to use a `\copydoc` but this can happen in other cases as well).
|
| |
|
|
|
|
| |
show merged descriptions
Set "ends brief description" for the different for the commands mentioned in issue (as well as addtogroup)
|
| |
|
|
|
|
| |
suspicious text
To escape `\` and `@` not only `\\` and `@@` should be possible but also `\@` and `@\`
|
| |
|
|
| |
With the list types `-`, `*` and `1.` the brief description is terminated, with the `-#` lists this was not the case.
|
| |
|
|
|
|
|
|
| |
The brief command is intended for a small description of a function / class / namespace etc. and not to have extensive formulas or code snippets. These commands should terminate the brief description and start the detailed section.
The commands `\snippet` and `\snippetlineno` are added to the list of commands to terminate the brief description.
The commands `\f[` and `\f{` are handled separately but now also start a detailed description.
The `\f$` is just for small formulas and thus possible in a brief description.
|
| | |
|
| |
|
|
| |
The `\f{..}` looks like the, new, option handling, but the handling if `\f{` is done at another place and would now be included here due to the first part `<Comment>{B}*{CMD}[a-z_A-Z]+"{"[a-zA-Z_,:0-9\. ]*"}"{B}*` of the rules.
|
| | |
|
| |
|
|
| |
In case no options specified with the `\tableofcontents` `Html` and `XML` should be generated and not only `Html` (compatibility).
|
| |
|
|
| |
output
|
| |
|
|
| |
In the `\cite` label some extra characters are enabled, '-' and '?', as the '--' and '---' have been converted beforehand they have to be converted back and the corresponding labels also have to between double quotes (which are striped away).
|
| |\
| |
| | |
Add commands to handle referenced by relation and references relation
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Shortened the commands:
- referencedbyrelation -> showrefby
- hidereferencedbyrelation -> hiderefby
- referencesrelation -> showrefs
- hidereferencesrelation -> hiderefs
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Analogous to call graph and caller graph this patch provides an implementation for the referenced by relation and references relation.
Providing the commands:
- referencedbyrelation
- hidereferencedbyrelation
- referencesrelation
- hidereferencesrelation
Motivation is that some lists can get extremely large and also there is now more symmetry between the textual and graphical out.
|
| |\ \
| |/
|/| |
Bug 748927 - Navigation incorrect with escaped symbols
|
| | |
| |
| |
| |
| | |
Due to the fact that constructs like `<my>` in a page title are seen as an XML-tag (with a resulting warning) the `<` should be escaped but this leads to the fact that the escape sign is shown in the bars on top of a HTML page.
The basic problem is due to the fact that page titles are not really interpreted by doxygen (as "nothing" can be, generically, handled in the title of a page.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Till now docbook had its own output generator, but lot of possibilities were missing (see remark about updating below), with this patch the (more than) basic implementation has been made.
Added some docbook tests to the current tests and updated documentation where necessary
Tried updating current version but too many issues remained that were generically handled in the standard generator, code is in current version behind '#if 0' construct in doxygen.cpp and name with '_v1' and in docbookgen.cp'
|
| | | |
|
| |/ |
|
| |\
| |
| | |
Typos found by running "codespell"
|
| | | |
|
| |\ \
| | |
| | | |
Bug 610436 - <![CDATA[ is not handled inside C# comments
|
| | | |
| | |
| | |
| | | |
Added handling of "<![CDATA[ ... ]]>" i.e. XML CDATA sections in an analogous way top HTML comment but in this case the text is retained (as normal doxygen comment) and the special XML characters `<`,`>` and `&` are taken as if they were escaped.
|
