+...@item --config +Print the configuration settingsPrint the arguments that were passed to @command{configure}.I've had a similar line in an early version of the patch. However, it's not *quite* correct, technically. We drop a few options when setting up $ac_configure_args (--no-create, --no-recursion, --silent, some duplicate arguments), and we add precious variables that came in from the environment. A configure script invoked by a higher-level one through recursion may be passed --srcdir and mangled --cache-file arguments. Also, we don't guard against the configure.ac author mangling $ac_configure_args. So, the above formulation seemed more cautious to me. But hey, if you think being explicit here is better, that's ok with me, too.
Yes, this explains it. It could be "print @command{configure} command-line arguments that will recreate this configuration", if that would help understanding what kind of settings are printed. But just go ahead and pick your favorite formulation without yet another iteration.
Paolo
