Add documentation for command print_named_configs

docs/command_line.rst

@@ -137,7 +137,7 @@ The name of the command has to be first on the commandline::
 
     >>> ./my_demo.py COMMAND_NAME with seed=123
 
-If the COMMAND_NAME is ommitted it defaults to the main function, but the name
+If the COMMAND_NAME is omitted it defaults to the main function, but the name
 of that function can also explicitly used as the name of the command.
 So for this experiment
 
@@ -263,6 +263,32 @@ The format for exporting the config is inferred from the filename and can be
 any format supported for :ref:`config files <config_files>`.
 
 
+.. _print_named_configs:
+
+Print Named Configs
+-------------------
+
+The ``print_named_configs`` command prints all available named configurations.
+Function docstrings for named config functions are copied and displayed colored
+in **grey**.
+For example::
+
+    >> ./named_config print_named_configs
+    INFO - hello_config - Running command 'print_named_configs'
+    INFO - hello_config - Started
+    Named Configurations (doc):
+      rude   # A rude named config
+    INFO - hello_config - Completed after 0:00:00
+
+If no named configs are available for the experiment, an empty list is printed::
+
+    >> ./01_hello_world print_named_configs
+    INFO - 01_hello_world - Running command 'print_named_configs'
+    INFO - 01_hello_world - Started
+    Named Configurations (doc):
+      No named configs
+    INFO - 01_hello_world - Completed after 0:00:00
+
 Custom Commands
 ---------------
 If you just run an experiment file it will execute the default command, that

examples/named_config.py

@@ -9,6 +9,7 @@
 
 @ex.named_config
 def rude():
+    """A rude named config"""
     recipient = "bastard"
     message = "Fuck off you {}!".format(recipient)