Lines Matching refs:line
53 # Using the PROJECT_BRIEF tag one can provide an optional one line description
202 # first line (until the first dot) of a Javadoc-style comment as the brief
210 # If the JAVADOC_BANNER tag is set to YES then Doxygen will interpret a line
221 # line (until the first dot) of a Qt-style comment as the brief description. If
229 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
231 # to treat a multi-line C++ comment block as a detailed description. Set this
934 # can produce. The string should contain the $file, $line, and $text tags, which
935 # will be replaced by the file and line number from which the warning originated
940 # The default value is: $file:$line: $text.
942 WARN_FORMAT = "$file:$line: $text"
948 # WARN_LINE_FORMAT = "'vi $file +$line'"
950 # The default value is: at line $line of file $file.
952 WARN_LINE_FORMAT = "at line $line of file $file"
1180 # multi-line macros, enums or list initialized variables directly into the
1236 # tools must be available from the command line (i.e. in the search path).
1273 # line options that you would normally use when invoking the compiler. Note that
1765 # Doxygen will group on one line in the generated HTML documentation.
2540 # remove all references to function-like macros that are alone on a line, have
2735 # to display on a single line. If the actual line length exceeds this threshold
2737 # applied to avoid ugly line breaks.
2920 # files in one run (i.e. multiple -o and -T options on the command line). This