gmid.1: some spelling, grammar and crosslinks

gmid.1: provide certificate generation example

gmid.1: document logging

use \e instead of \\ as a mean to escape \ Just read in a mail from Ingo to tech@ > Using \\ outside macro definitions (i.e., outside the bodies of roff(7) > .de and similar requests) is almost always wrong even in low-level roff > code, and \\ must never be used in manual pages.

tag v1.7.1 This version includes two bugfixes: - use ${MAKE} to recursively call make - fix the misleading example in the man page: macros name may not be reserved words Both bugs found and fixed by Anna “CyberTailor”, thanks!

align

fix misleading example in man page > Macros names may not be reserved words

tag v1.7

sync macro usage and mention the `include' keyword

`param' is forbidden inside `location's too and while there sort the list of disallowed rules.

misc improvements to the manual

change (again) the env/param separator: use '=' Given that env/param are new features of this release, no support for the "old" syntax is needed.

add => in env/param and `port' between hostname and port for fastcgi In the same spite of the last commit, add the missing separators between strings to avoid the auto-concat pitfalls. `=>' is used to separate between `env' and `param' arguments, while for `fastcgi' the keyword `port' is required between the hostname/ip address and the port (if provided). Since `env', `param' and `fastcgi' are all new stuff, there's no need to keep compatibility.

rename `mime MIME EXT' to `map MIME to-ext EXT' With the newish automatic string concatenation, options like `mime' that accepts two strings as parameter start to become ambiguous: which strings gets concatenated? Instead of trying to document in the manpage which argument(s) is subject to string concatenation, do the concat always and introduce a separator. In the case of mime, `to-ext' now acts as a separator to distinguish. While there, also use a new keyword because it sounds better. It's dead-easy to upgrade to the new configuration, possibly with some sed magic, but for the moment the old `mime' form is preserved: (with a warning!) Will be dropped in the next release.

revert 2c16dbd5486 -- macro names can't be reserved words While one can define a macro using a reserved word as name using -Dname=val, inside the configuration file it'll fail.