class Gem::Commands::EnvironmentCommand

def description # :nodoc:
  <<-EOF
e environment command lets you query rubygems for its configuration for
e in shell scripts or as a debugging aid.
e RubyGems environment can be controlled through command line arguments,
mrc files, environment variables and built-in defaults.
mmand line argument defaults and some RubyGems defaults can be set in a
.gemrc file for individual users and a gemrc in the SYSTEM CONFIGURATION
RECTORY for all users. These files are YAML files with the following YAML
ys:
:sources: A YAML array of remote gem repositories to install gems from
:verbose: Verbosity of the gem command. false, true, and :really are the
          levels
:update_sources: Enable/disable automatic updating of repository metadata
:backtrace: Print backtrace when RubyGems encounters an error
:gempath: The paths in which to look for gems
:disable_default_gem_server: Force specification of gem server host on push
<gem_command>: A string containing arguments for the specified gem command
ample:
:verbose: false
install: --no-wrappers
update: --no-wrappers
:disable_default_gem_server: true
byGems' default local repository can be overridden with the GEM_PATH and
M_HOME environment variables. GEM_HOME sets the default repository to
stall into. GEM_PATH allows multiple local repositories to be searched for
ms.
 you are behind a proxy server, RubyGems uses the HTTP_PROXY,
TP_PROXY_USER and HTTP_PROXY_PASS environment variables to discover the
oxy server.
 you would like to push gems to a private gem server the RUBYGEMS_HOST
vironment variable can be set to the URI for that server.
 you are packaging RubyGems all of RubyGems' defaults are in
b/rubygems/defaults.rb.  You may override these in
b/rubygems/defaults/operating_system.rb
  EOF
end