Lines Matching +refs:clang +refs:format +refs:fallback +refs:style

403 write the definition in pre-standard style like this,
417 the function definition in the pre-standard style.
728 When an error is spread over several files, you can use this format:
743    If you want to mention the column number, use this format:
752 would do best to print error messages using the noninteractive style.)
794 `ls' except that its default output format is always multi-column
795 format.
834 single-letter Unix-style options.  We hope to make GNU more user
877 contains the canonical name for this program, in this format:
898 library you want to mention.  Use the same format for these lines as for
1025 help using GNU programs.  The format should be like this:
1374 `footnote-style'
1387 `format'
2029 `suffix-format'
2303 using Standard C syntax, the format is this:
2311 or, if you want to use traditional C syntax, format the definition like
2340 of C formatting style, which is also the default style of the `indent'
2350    But whatever style you use, please use it consistently, since a
2352 contributing changes to an existing program, please follow the style of
2355    For the body of the function, our recommended style looks like this:
2521 such as `lint', `clang', and GCC with extra warnings options such as
2702    Avoid using the format of semi-internal data bases (e.g.,
2927 by adding `s'.  If you apply gettext to the format string, like this,
3000 the option `--quoting-style' of GNU `ls'.
3052 The preferred document format for the GNU system is the Texinfo
3139 course, some exceptions.)  Also, Unix man pages use a particular format
3172 Meanwhile, it can be rather informal in style.
3936    If you use symbolic links, you should implement a fallback for
4284      format.  They should all be set to `$(docdir)' by default.  (If
4317    Unix-style man pages are installed in one of the following:
4408      documentation format) files should be made only when explicitly
4485      the package, if that format is desired.  GNU prefers Info files,
4617      Generate documentation files in the given format.  These targets
4619      output format cannot be generated.  These targets should not be
5084      represented in a format whose specification is available to the
5091      otherwise Transparent file format whose markup, or absence of
5093      modification by readers is not Transparent.  An image format is
5098      ASCII without markup, Texinfo input format, LaTeX input format,
5526 * change logs, style:                    Style of Change Logs.
5529 * clang:                                 Syntactic Conventions.