anchor.diff:  gremlin> :plugin list  <1>
   ==>tinkerpop.server[active]
   ==>tinkerpop.gephi
  +==>tinkerpop.utilities[active]
   ==>tinkerpop.sugar
  -==>tinkerpop.utilities[active]
  +==>tinkerpop.tinkergraph[active]
   gremlin> :plugin use tinkerpop.sugar  <2>
   ==>tinkerpop.sugar activated
   gremlin> :install com.tinkerpop neo4j-gremlin x.y.z  <3>
  
positive.code: <4> Note that there is a "tinkerpop.neo4j" plugin available, but it is not yet "active".
  <5> Again, to use the "tinkerpop.neo4j" plugin, it must be made "active" with `:plugin use`.
  <6> Now when the plugin list is displayed, the "tinkerpop.neo4j" plugin is displayed as "active".
  
  NOTE: The Gremlin Console comes configured with a number of plugins configured as "active" by default (such as "tinkerpop.server").  These plugins and other pre-packaged plugins cannot be removed from the Console as they are a part of the `gremlin-console.jar` itself.  These plugins can only be deactivated.
  
  CAUTION: 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.
  
  
negative.code: ==>tinkerpop.sugar[active]
  ==>tinkerpop.utilities[active]
  ==>tinkerpop.neo4j[active]
  ==>tinkerpop.tinkergraph[active]
  ----
  
  <1> Show a list of "available" plugins.  The list of "available" plugins is determined by the classes available on the Console classpath.  Plugins need to be "active" for their features to be available.
  