reorganize octave_config_info again * build-env-features.sh: Don't include ENABLE_ items in the output. * toplev.cc (find_config_info): New static function. (Foctave_config_info): Put Octave configuration info in the main struct. Put the build system features and build environment info in substructures. Allow searching of all elements by keyword. * __have_feature__.m, doc/interpreter/testfun.txi: Fix name of build features substructure element. * geometryimages.m, interpimages.m, plotimages.m, sparseimages.m, splineimages.m: Use __have_feature__ to check for OSMESA.

--- a/doc/interpreter/testfun.txi	Mon Feb 08 17:34:12 2016 -0500
+++ b/doc/interpreter/testfun.txi	Mon Feb 08 23:14:56 2016 -0500
@@ -141,8 +141,8 @@
 @end example
 
 @noindent
-Review @file{config.h} or @code{octave_config_info ("features")} to see some
-of the possible values to check.
+Review @file{config.h} or @code{octave_config_info ("build_features")}
+to see some of the possible values to check.
 
 Sometimes during development there is a test that should work but is
 known to fail.  You still want to leave the test in because when the