3 configfile \- generic configuration file format
11 The syntax of the generic configuration file format is as follows:
18 | configline configfile
22 configline: wordlist '\fB;\fR'
24 | \fBinclude\fR string '\fB;\fR'
32 | '\fB{\fR' configfile '\fB}\fR' wordlist
39 A word is a sequence of letters, numbers, and characters from the set
40 .BR "!#$%&*+-./<=>?[\e]^_|~" .
43 may be followed by a character in the set
45 to form a BEL, BS, ESC, FF, NL, CR, SP, TAB, or VT character. Followed by
46 up to three octal digits a character of that value is formed, and likewise
49 followed by up to two hexadecimal digits. Any other character is left
50 as-is. A backslash followed by whitespace is completely removed from the
51 input. (This includes comments.)
53 A string is started by a single or double quote, a series of characters, and
54 ended by the same type of quote it started with. Any character or
57 may be found in a string. Strings may not span lines.
59 Tokens are separated by whitespace, being the usual whitespace characters
60 and comments. A comment starts with the
62 character, and ends at a newline.
66 tells that the file mentioned in the following string must be read and
67 included at that point. The file is found relative to the directory the
68 current configuration file is found in, unless its name starts with a
70 A file that doesn't exist is seen as empty.
72 A generic configuration file can be read with the functions described in
80 Inspired by the configuration file of Paul Vixie's
83 Kees J. Bot (kjb@cs.vu.nl)