Any option that is not marked as not presettable may be preset by loading values from configuration ("rc" or "ini") files.
libopts will search in $HOME for configuration (option) data.
The environment variable
HOME, is expanded and replaced when
the program runs
If this is a plain file, it is simply processed.
If it is a directory, then a file named .sharrc is searched for within that directory.
Configuration files may be in a wide variety of formats. The basic format is an option name followed by a value (argument) on the same line. Values may be separated from the option name with a colon, equal sign or simply white space. Values may be continued across multiple lines by escaping the newline with a backslash.
Multiple programs may also share the same initialization file. Common options are collected at the top, followed by program specific segments. The segments are separated by lines like:
Do not mix these styles within one configuration file.
Compound values and carefully constructed string values may also be specified using XML syntax:
<option-name> <sub-opt>...<...>...</sub-opt> </option-name>
option-name.sub-opt string value of
AutoOpts does not track suboptions. You simply note that it is a
hierarchicly valued option.
AutoOpts does provide a means for searching
the associated name/value pair list (see: optionFindValue).
The command line options relating to configuration and/or usage help are:
Print the program version to standard out, optionally with licensing information, then exit 0. The optional argument specifies how much licensing detail to provide. The default is to print the license name with the version. The licensing infomation may be selected with an option argument. Only the first letter of the argument is examined: