If user wants to interpret the SemVer they can use one of modules
available for this purpose or do their own "cutting".

to easily test out documentation for currently developed library.

which is somehow better than "random" order.

Use of `;&` instead of `|` yields the same behavior, but is much easier
to read if number of alternatives is longer.

 *  Re-use code provided by `-e` as function exit status.

 *  Default to FFOO_EXITS_USAGE, i.e. 2.

 *  Add -k as shorthand for `-e 0`.

 *  Update and enhance docstring.

`echos()` is implemented using `printf` with format argument containing
one `%s` and newline.  `printf` behavior is to repeat the format for
any excessive arguments, so that we may end up with multiple lines:

>     $ printf -- "%s\n" 1
>     1
>     $ printf -- "%s\n" 1 2
>     1
>     2

Since use of `"$@"` is often recommended as default, frontend call like
`think "args: $@"` are to be expected.  This way arguments are split
automatically,  however, traditional `echo` would normally join them back
to one line.  It's more intuitive to have the same behavior by default.

Using `"$*"` in __echo_args results in joining all parameters back to
single line, resulting in printf calls similar to this:

>     $ printf -- "%s\n" "1"
>     1
>     $ printf -- "%s\n" "1 2"
>     1 2

Note that user can still use `-l` argument to switch to __echo_lines
should they really want to have each argument printed on a separate line
(but that's a different story).

Do not touch world on importing, use explicit function for empdir
creation.

git-describe will prefer annotated tags, git-log has much more straightforward solution

Ans its internal sub-modules to _pretty_*

Including two failing ones

Generalize color codes per function and leave them empty if a "real
pipe" (i.e. pipe or file) is detected[1] on STDERR (2).

 [1]: http://stackoverflow.com/questions/911168/how-to-detect-if-my-shell-script-is-running-through-a-pipe

In this case it's simpler--no need to detect end case and no need to
shift, i.e. less typing/reading.

Now testname.oracle file can specify expected exit status file
as well, or different path for stdout/stderr oracles (default is
testname.oracle.stdout and testname.oracle.stderr)

This effectively allows for testing scenarios where exit status or error
output can be tested as well.