anchor.diff:  
   WARNING: Plugins must be compatible with the version of the Gremlin Console (or Gremlin Server) being used.  Attempts
   to use incompatible versions cannot be guaranteed to work.  Moreover, be prepared for dependency conflicts in
  -third-party plugins, that may only be resolved via manual jar removal from the `ext/{plugin}` directory.
  +third-party plugins that may only be resolved via manual jar removal from the `ext/{plugin}` directory.
   
   TIP: It is possible to manage plugin activation and deactivation by manually editing the `ext/plugins.txt` file which
   contains the class names of the "active" plugins.  It is also possible to clear dependencies added by `:install` by
  
positive.code: |import |:i |Import a class into the Console session.
  |:clear |:c |Sometimes the Console can get into a state where the command buffer no longer understands input (e.g. a misplaced `(` or `}`).  Use this command to clear that buffer.
  |:load |:l |Load a file or URL into the command buffer for execution.
  |:install |:+ |Imports a maven library and its dependencies into the Console.
  |:uninstall |:- |Removes a maven library and its dependencies. A restart of the console is required for removal to fully take effect.
  |:plugin |:pin |Plugin management functions to list, activate and deactivate available plugins.
  |:remote |:rem |Configures a "remote" context where Gremlin or results of Gremlin will be processed via usage of `:submit`.
  |:submit |:> |Submit Gremlin to the currently active context defined by `:remote`.
  |:bytecode |:bc |Provides options for translating and evaluating `Bytecode` for debugging purposes.
  |=========================================================
  
  Many of the above commands are described elsewhere or are generally self explanatory, but the `:bytecode` command
  could use some additional explanation. The following code shows example usage:
  
  [source,text]
  
negative.code: 
  * Allows any Gremlin Structure-enabled graph to exist as a standalone server, which in turn enables the ability for
  multiple clients to communicate with the same graph database.
  * Enables execution of ad hoc queries through remotely submitted Gremlin scripts.
  * Allows for the hosting of Gremlin-based DSLs (Domain Specific Language) that expand the Gremlin language to match
  the language of the application domain, which will help support common graph use cases such as searching, ranking,
  and recommendation.
  