mod_autoindex: clarify that =value options are not cleared by unprefixed keywords...

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933762 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/mod/mod_autoindex.xml b/docs/manual/mod/mod_autoindex.xml
index 2df9aa57cd655ee28b20c6d35b22b7b245667ce7..a4cba5311341ee46476261bf37d019dcc4ed5fc6 100644 (file)
--- a/docs/manual/mod/mod_autoindex.xml
+++ b/docs/manual/mod/mod_autoindex.xml
@@ -1007,7 +1007,12 @@ indexing</description>
      settings (which may have been inherited from an upper-level
      directory). However, whenever an unprefixed keyword is processed, it
      clears all inherited options and any incremental settings encountered
-     so far. Consider the following example:</p>
+     so far, except for options that take a value
+     (<code>Charset</code>, <code>Type</code>,
+     <code>DescriptionWidth</code>, <code>NameWidth</code>,
+     <code>IconWidth</code>, <code>IconHeight</code>),
+     which are inherited independently.
+     Consider the following example:</p>
 
      <highlight language="config">
 IndexOptions +ScanHTMLTitles -IconsAreLinks FancyIndexing