7.11.4 configuration file directives

The <? marker indicates an XML directive. There is only one directive supported: program sectioning, though two syntaxes are supported.

If, for example, you have a collection of programs that work closely together and, likely, have a common set of options, these programs may use a single, sectioned, configuration file. The file may be sectioned in either of two ways. The two ways may not be intermixed in a single configuration file. All text before the first segmentation line is processed, then only the segment that applies:

‘<?auto-options ...>’

The ... ellipsis may contain AutoOpts option processing options. Currently, that consists of one or both of:

gnu

autoopts

to indicate GNU-standard or AutoOpts-standard layout of usage and version information, and/or

misuse-usage

no-misuse-usage

to indicate whether the available options should be listed when an invalid option appears on the command line.

Anything else will be silently ignored.

‘<?program prog-name>’

The <? marker indicates an XML directive. The file is partitioned by these lines and the options are processed for the prog-name program only before the first <?program directive and the program section with a matching program name.

‘[PROG_NAME]’

This is basically an alias for <?program prog-name>, except that the program name must be upper cased and segmented only with underscores.

Segmentation does not apply if the config file is being parsed with the configFileLoad(3AutoOpts) function.

This document was generated by Bruce Korb on August 21, 2015 using texi2html 1.82.