Addition of the --no-index flag to the analysis server spec.

pkg/analysis_server/tool/spec/spec_input.html

Index: pkg/analysis_server/tool/spec/spec_input.html
diff --git a/pkg/analysis_server/tool/spec/spec_input.html b/pkg/analysis_server/tool/spec/spec_input.html
index b34defb8751f535336ced91af810f2b5ee785e05..3c6a8057ee1fcba5001ca84c3429ac70af374f6b 100644
--- a/pkg/analysis_server/tool/spec/spec_input.html
+++ b/pkg/analysis_server/tool/spec/spec_input.html
@@ -162,6 +162,17 @@
       </ul>
       </dd>
     </dl>
+    <dl>
+      <dt>--no-index</dt>
+      <dd>
+      An indication that no indexer calls will be made to the analysis server,

[Brian Wilkerson, 2015/02/17 17:54:46]

"An indication" seems a little weak. The flag explicitly tells server not to
create an index.

+      and thus, no index should be created. If this flag is passed and an API is
+      used that requires an index, then an <tt>NO_INDEX_GENERATED</tt> exception

[Brian Wilkerson, 2015/02/17 17:54:46]

"an" --> "a"
"exception" --> "error"

+      will be thrown. The set of API calls that require an index include:
+      refactoring calls, code completions and searching.

[scheglov, 2015/02/17 17:48:36]

Would be nice to document also corresponding API requests and state that they
return this error if no index was generated. So, we would remind users that this
API might not work.

[jwren, 2015/02/17 17:54:41]

Agreed.  After we know what the set of APIs are, I'll go through and do this.

[Brian Wilkerson, 2015/02/17 17:54:46]

I think we need to actually include this information in each individual request
that can generate this error. Otherwise (a) it's hard for clients to remember
which calls will generate the error and (b) the list will get out of date.

+      <!-- TODO(jwren/scheglov): make sure that this of APIs that is complete. -->
+      </dd>
+    </dl>
     </blockquote>
     <domain name="server">
       <p>
@@ -3097,7 +3108,7 @@
           <value>
             <code>INVALID_OVERLAY_CHANGE</code>
             <p>
-              An analysis.updateContent request contained a
+              An "analysis.updateContent" request contained a

[Brian Wilkerson, 2015/02/17 17:54:46]

I don't think we quote request/notification names elsewhere. We should be
consistent.

               ChangeContentOverlay object which can't be applied, due
               to an edit having an offset or length that is out of
               range.
@@ -3116,6 +3127,13 @@
             </p>
           </value>
           <value>
+            <code>NO_INDEX_GENERATED</code>
+            <p>
+              The "--no-index" flag was passed when the analysis server created,

[Brian Wilkerson, 2015/02/17 17:54:46]

"server created" --> "server was created"

+              but this API call requires an index to have been generated.
+            </p>
+          </value>
+          <value>
             <code>REFACTORING_REQUEST_CANCELLED</code>
             <p>
               Another refactoring request was received during processing of