Lines Matching refs:line

53 # Using the PROJECT_BRIEF tag one can provide an optional one line description
206 # first line (until the first dot) of a Javadoc-style comment as the brief
214 # If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line
225 # line (until the first dot) of a Qt-style comment as the brief description. If
233 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
235 # to treat a multi-line C++ comment block as a detailed description. Set this
907 # can produce. The string should contain the $file, $line, and $text tags, which
908 # will be replaced by the file and line number from which the warning originated
913 # The default value is: $file:$line: $text.
915 WARN_FORMAT            = "$file:$line: $text"
921 # WARN_LINE_FORMAT = "'vi $file +$line'"
923 # The default value is: at line $line of file $file.
925 WARN_LINE_FORMAT       = "at line $line of file $file"
1232 # tools must be available from the command line (i.e. in the search path).
1697 # doxygen will group on one line in the generated HTML documentation.
2374 # remove all references to function-like macros that are alone on a line, have
2565 # to display on a single line. If the actual line length exceeds this threshold
2567 # to avoid ugly line breaks.
2750 # files in one run (i.e. multiple -o and -T options on the command line). This