bundler 1.16.0 → 1.16.1

data/man/bundle-viz.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-VIZ" "1" "October 2017" "" ""
+.TH "BUNDLE\-VIZ" "1" "July 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\-viz\fR \- Generates a visual dependency graph for your Gemfile

data/man/bundle-viz.1.txt

@@ -2,37 +2,37 @@ BUNDLE-VIZ(1)							 BUNDLE-VIZ(1)
 
 
 
-1mNAME0m
-       1mbundle-viz 22m- Generates a visual dependency graph for your Gemfile
+NAME
+       bundle-viz - Generates a visual dependency graph for your Gemfile
 
-1mSYNOPSIS0m
-       1mbundle viz 22m[--file=FILE] [--format=FORMAT] [--requirements] [--version]
+SYNOPSIS
+       bundle viz [--file=FILE] [--format=FORMAT] [--requirements] [--version]
        [--without=GROUP GROUP]
 
-1mDESCRIPTION0m
-       1mviz 22mgenerates a PNG file of the  current  1mGemfile(5)  22mas  a  dependency
-       graph. 1mviz 22mrequires the ruby-graphviz gem (and its dependencies).
+DESCRIPTION
+       viz generates a PNG file of the	current  Gemfile(5)  as  a  dependency
+       graph. viz requires the ruby-graphviz gem (and its dependencies).
 
-       The associated gems must also be installed via 1mbundle install(1)22m.
+       The associated gems must also be installed via bundle install(1).
 
-1mOPTIONS0m
-       1m--file22m, 1m-f0m
-	      The name to use for the generated file. See 1m--format 22moption
+OPTIONS
+       --file, -f
+	      The name to use for the generated file. See --format option
 
-       1m--format22m, 1m-F0m
+       --format, -F
 	      This is output format option. Supported format is png, jpg, svg,
 	      dot ...
 
-       1m--requirements22m, 1m-R0m
+       --requirements, -R
 	      Set to show the version of each required dependency.
 
-       1m--version22m, 1m-v0m
+       --version, -v
 	      Set to show each gem version.
 
-       1m--without22m, 1m-W0m
+       --without, -W
 	      Exclude gems that are part of the specified named group.
 
 
 
 
-				 October 2017			 BUNDLE-VIZ(1)
+				   July 2017			 BUNDLE-VIZ(1)

data/man/bundle.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE" "1" "October 2017" "" ""
+.TH "BUNDLE" "1" "July 2017" "" ""
 .
 .SH "NAME"
 \fBbundle\fR \- Ruby Dependency Management

data/man/bundle.1.txt

@@ -2,112 +2,112 @@ BUNDLE(1)							     BUNDLE(1)
 
 
 
-1mNAME0m
-       1mbundle 22m- Ruby Dependency Management
+NAME
+       bundle - Ruby Dependency Management
 
-1mSYNOPSIS0m
-       1mbundle 22mCOMMAND [--no-color] [--verbose] [ARGS]
+SYNOPSIS
+       bundle COMMAND [--no-color] [--verbose] [ARGS]
 
-1mDESCRIPTION0m
-       Bundler	manages  an 1mapplication's dependencies 22mthrough its entire life
+DESCRIPTION
+       Bundler	manages  an application's dependencies through its entire life
        across many machines systematically and repeatably.
 
-       See the bundler website 4mhttp://bundler.io24m for  information	on  getting
-       started, and Gemfile(5) for more information on the 1mGemfile 22mformat.
+       See the bundler website http://bundler.io for  information  on  getting
+       started, and Gemfile(5) for more information on the Gemfile format.
 
-1mOPTIONS0m
-       1m--no-color0m
+OPTIONS
+       --no-color
 	      Print all output without color
 
-       1m--retry22m, 1m-r0m
+       --retry, -r
 	      Specify the number of times you wish to attempt network commands
 
-       1m--verbose22m, 1m-V0m
+       --verbose, -V
 	      Print out additional logging information
 
-1mBUNDLE COMMANDS0m
-       We divide 1mbundle 22msubcommands into primary commands and utilities.
+BUNDLE COMMANDS
+       We divide bundle subcommands into primary commands and utilities.
 
-1mPRIMARY COMMANDS0m
-       [1mbundle install(1)22m][bundle-install]
-	      Install the gems specified by the 1mGemfile 22mor 1mGemfile.lock0m
+PRIMARY COMMANDS
+       [bundle install(1)][bundle-install]
+	      Install the gems specified by the Gemfile or Gemfile.lock
 
-       [1mbundle update(1)22m][bundle-update]
+       [bundle update(1)][bundle-update]
 	      Update dependencies to their latest versions
 
-       [1mbundle package(1)22m][bundle-package]
-	      Package  the  .gem  files  required by your application into the
-	      1mvendor/cache 22mdirectory
+       [bundle package(1)][bundle-package]
+	      Package the .gem files required by  your	application  into  the
+	      vendor/cache directory
 
-       [1mbundle exec(1)22m][bundle-exec]
+       [bundle exec(1)][bundle-exec]
 	      Execute a script in the context of the current bundle
 
-       [1mbundle config(1)22m][bundle-config]
+       [bundle config(1)][bundle-config]
 	      Specify and read configuration options for bundler
 
-       1mbundle help(1)0m
+       bundle help(1)
 	      Display detailed help for each subcommand
 
-1mUTILITIES0m
-       1mbundle add(1)0m
-	      Add the named gem to the Gemfile and run 1mbundle install0m
+UTILITIES
+       bundle add(1)
+	      Add the named gem to the Gemfile and run bundle install
 
-       1mbundle binstubs(1)0m
+       bundle binstubs(1)
 	      Generate binstubs for executables in a gem
 
-       1mbundle check(1)0m
-	      Determine whether the  requirements  for	your  application  are
+       bundle check(1)
+	      Determine  whether  the  requirements  for  your application are
 	      installed and available to bundler
 
-       1mbundle show(1)0m
+       bundle show(1)
 	      Show the source location of a particular gem in the bundle
 
-       [1mbundle outdated(1)22m][bundle-outdated]
+       [bundle outdated(1)][bundle-outdated]
 	      Show all of the outdated gems in the current bundle
 
-       1mbundle console(1)0m
+       bundle console(1)
 	      Start an IRB session in the context of the current bundle
 
-       1mbundle open(1)0m
+       bundle open(1)
 	      Open an installed gem in the editor
 
-       [1mbundle lock(1)22m][bundle-lock]
+       [bundle lock(1)][bundle-lock]
 	      Generate a lockfile for your dependencies
 
-       1mbundle viz(1)0m
+       bundle viz(1)
 	      Generate a visual representation of your dependencies
 
-       1mbundle init(1)0m
-	      Generate a simple 1mGemfile22m, placed in the current directory
+       bundle init(1)
+	      Generate a simple Gemfile, placed in the current directory
 
-       [1mbundle gem(1)22m][bundle-gem]
+       [bundle gem(1)][bundle-gem]
 	      Create a simple gem, suitable for development with bundler
 
-       [1mbundle platform(1)22m][bundle-platform]
+       [bundle platform(1)][bundle-platform]
 	      Display platform compatibility information
 
-       1mbundle clean(1)0m
+       bundle clean(1)
 	      Clean up unused gems in your bundler directory
 
-       1mbundle doctor(1)0m
+       bundle doctor(1)
 	      Display warnings about common potential problems
 
-1mPLUGINS0m
-       When  running a command that isn't listed in PRIMARY COMMANDS or UTILI-
-       TIES, Bundler will try  to  find  an  executable  on  your  path  named
-       1mbundler-<command>  22mand  execute it, passing down any extra arguments to
+PLUGINS
+       When running a command that isn't listed in PRIMARY COMMANDS or	UTILI-
+       TIES,  Bundler  will  try  to  find  an	executable  on your path named
+       bundler-<command> and execute it, passing down any extra  arguments  to
        it.
 
-1mOBSOLETE0m
+OBSOLETE
        These commands are obsolete and should no longer be used
 
-       o   1mbundle cache(1)0m
+       o   bundle cache(1)
 
-       o   1mbundle show(1)0m
+       o   bundle show(1)
 
 
 
 
 
 
-				 October 2017			     BUNDLE(1)
+				   July 2017			     BUNDLE(1)

data/man/gemfile.5

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "GEMFILE" "5" "October 2017" "" ""
+.TH "GEMFILE" "5" "July 2017" "" ""
 .
 .SH "NAME"
 \fBGemfile\fR \- A format for describing gem dependencies for Ruby programs

data/man/gemfile.5.txt

@@ -2,24 +2,24 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mNAME0m
-       1mGemfile 22m- A format for describing gem dependencies for Ruby programs
+NAME
+       Gemfile - A format for describing gem dependencies for Ruby programs
 
-1mSYNOPSIS0m
-       A 1mGemfile 22mdescribes the gem dependencies required to execute associated
+SYNOPSIS
+       A Gemfile describes the gem dependencies required to execute associated
        Ruby code.
 
-       Place the 1mGemfile 22min the root of the directory containing  the  associ-
-       ated  code.  For instance, in a Rails application, place the 1mGemfile 22min
-       the same directory as the 1mRakefile22m.
+       Place the Gemfile in the root of the directory containing  the  associ-
+       ated  code.  For instance, in a Rails application, place the Gemfile in
+       the same directory as the Rakefile.
 
-1mSYNTAX0m
-       A 1mGemfile 22mis evaluated as Ruby code, in a context which makes available
+SYNTAX
+       A Gemfile is evaluated as Ruby code, in a context which makes available
        a number of methods used to describe the gem requirements.
 
-1mGLOBAL SOURCES0m
-       At the top of the 1mGemfile22m, add a line for the 1mRubygems 22msource that con-
-       tains the gems listed in the 1mGemfile22m.
+GLOBAL SOURCES
+       At the top of the Gemfile, add a line for the Rubygems source that con-
+       tains the gems listed in the Gemfile.
 
 
 
@@ -28,18 +28,18 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        It is possible, but not recommended as of Bundler 1.7, to add  multiple
-       global  1msource  22mlines.  Each  of these 1msource22ms 1mMUST 22mbe a valid Rubygems
+       global  source  lines.  Each  of these sources MUST be a valid Rubygems
        repository.
 
        Sources are checked for gems  following	the  heuristics  described  in
-       4mSOURCE24m  4mPRIORITY24m.  If	a  gem	is found in more than one global source,
+       SOURCE  PRIORITY.  If  a  gem  is found in more than one global source,
        Bundler will print a warning after installing the gem indicating  which
        source  was used, and listing the other sources where the gem is avail-
        able. A specific source can be selected for gems that  need  to	use  a
-       non-standard repository, suppressing this warning, by using the 1m:source0m
-       option or a 1msource 22mblock.
+       non-standard repository, suppressing this warning, by using the :source
+       option or a source block.
 
-   1mCREDENTIALS0m
+   CREDENTIALS
        Some gem sources require a username  and  password.  Use  [bundle  con-
        fig(1)][bundle-config]  to set the username and password for any of the
        sources that need it. The command must be run  once  on	each  computer
@@ -62,14 +62,14 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        Credentials in the source URL will take precedence over credentials set
-       using 1mconfig22m.
+       using config.
 
-1mRUBY0m
+RUBY
        If your application requires a specific Ruby version or engine, specify
-       your  requirements using the 1mruby 22mmethod, with the following arguments.
-       All parameters are 1mOPTIONAL 22munless otherwise specified.
+       your  requirements using the ruby method, with the following arguments.
+       All parameters are OPTIONAL unless otherwise specified.
 
-   1mVERSION (required)0m
+   VERSION (required)
        The version of Ruby that your application requires. If your application
        requires  an  alternate	Ruby  engine,  such as JRuby or Rubinius, this
        should be the Ruby version that the engine is compatible with.
@@ -80,32 +80,32 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mENGINE0m
-       Each application 4mmay24m specify a Ruby engine. If an engine is  specified,
-       an engine version 4mmust24m also be specified.
+   ENGINE
+       Each application may specify a Ruby engine. If an engine is  specified,
+       an engine version must also be specified.
 
        What  exactly is an Engine? - A Ruby engine is an implementation of the
        Ruby language.
 
        o   For background: the reference or  original  implementation  of  the
 	   Ruby   programming  language  is  called  Matz's  Ruby  Interpreter
-	   4mhttps://en.wikipedia.org/wiki/Ruby_MRI24m, or MRI for short.  This  is
+	   https://en.wikipedia.org/wiki/Ruby_MRI, or MRI for short.  This  is
 	   named  after  Ruby  creator Yukihiro Matsumoto, also known as Matz.
 	   MRI is also known as CRuby, because it is written in C. MRI is  the
 	   most widely used Ruby engine.
 
-       o   Other  implementations  4mhttps://www.ruby-lang.org/en/about/24m of Ruby
+       o   Other  implementations  https://www.ruby-lang.org/en/about/ of Ruby
 	   exist. Some of the more well-known implementations include Rubinius
-	   4mhttps://rubinius.com/24m,	and JRuby 4mhttp://jruby.org/24m. Rubinius is an
+	   https://rubinius.com/,  and JRuby http://jruby.org/. Rubinius is an
 	   alternative implementation of Ruby written in  Ruby.  JRuby	is  an
-	   implementation of Ruby on the JVM, short for Java Virtual Machine.
+	   implementation  of Ruby on the JVM, short for Java Virtual Machine.
 
 
 
-   1mENGINE VERSION0m
-       Each  application  4mmay24m specify a Ruby engine version. If an engine ver-
-       sion is specified, an engine 4mmust24m also be specified. If the  engine  is
-       "ruby" the engine version specified 4mmust24m match the Ruby version.
+   ENGINE VERSION
+       Each application may specify a Ruby engine version. If an  engine  ver-
+       sion  is  specified, an engine must also be specified. If the engine is
+       "ruby" the engine version specified must match the Ruby version.
 
 
 
@@ -113,8 +113,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mPATCHLEVEL0m
-       Each application 4mmay24m specify a Ruby patchlevel.
+   PATCHLEVEL
+       Each application may specify a Ruby patchlevel.
 
 
 
@@ -122,12 +122,12 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mGEMS0m
-       Specify gem requirements using the 1mgem 22mmethod, with the following argu-
-       ments. All parameters are 1mOPTIONAL 22munless otherwise specified.
+GEMS
+       Specify gem requirements using the gem method, with the following argu-
+       ments. All parameters are OPTIONAL unless otherwise specified.
 
-   1mNAME (required)0m
-       For each gem requirement, list a single 4mgem24m line.
+   NAME (required)
+       For each gem requirement, list a single gem line.
 
 
 
@@ -135,8 +135,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mVERSION0m
-       Each 4mgem24m 1mMAY 22mhave one or more version specifiers.
+   VERSION
+       Each gem MAY have one or more version specifiers.
 
 
 
@@ -145,10 +145,10 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mREQUIRE AS0m
-       Each 4mgem24m 1mMAY 22mspecify files that should be used when  autorequiring  via
-       1mBundler.require22m.  You  may pass an array with multiple files or 1mtrue 22mif
-       file you want 1mrequired 22mhas same name as 4mgem24m or  1mfalse  22mto  prevent  any
+   REQUIRE AS
+       Each  gem  MAY specify files that should be used when autorequiring via
+       Bundler.require. You may pass an array with multiple files or  true  if
+       file  you  want	required  has same name as gem or false to prevent any
        file from being autorequired.
 
 
@@ -159,7 +159,7 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       The  argument  defaults	to the name of the gem. For example, these are
+       The argument defaults to the name of the gem. For  example,  these  are
        identical:
 
 
@@ -170,9 +170,9 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mGROUPS0m
-       Each 4mgem24m 1mMAY 22mspecify membership in one or more  groups.  Any  4mgem24m  that
-       does  not  specify  membership  in  any	group is placed in the 1mdefault0m
+   GROUPS
+       Each  gem  MAY  specify	membership in one or more groups. Any gem that
+       does not specify membership in any  group  is  placed  in  the  default
        group.
 
 
@@ -182,8 +182,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       The Bundler runtime allows its  two  main  methods,  1mBundler.setup  22mand
-       1mBundler.require22m, to limit their impact to particular groups.
+       The  Bundler  runtime  allows  its  two main methods, Bundler.setup and
+       Bundler.require, to limit their impact to particular groups.
 
 
 
@@ -202,9 +202,9 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       The  Bundler CLI allows you to specify a list of groups whose gems 1mbun-0m
-       1mdle install 22mshould not install with the 1m--without  22moption.  To  specify
-       multiple  groups  to ignore, specify a list of groups separated by spa-
+       The Bundler CLI allows you to specify a list of groups whose gems  bun-
+       dle  install  should  not install with the --without option. To specify
+       multiple groups to ignore, specify a list of groups separated  by  spa-
        ces.
 
 
@@ -214,46 +214,46 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       After running 1mbundle install --without test22m, bundler will remember that
+       After running bundle install --without test, bundler will remember that
        you excluded the test group in the last installation. The next time you
-       run 1mbundle install22m, without any 1m--without option22m, bundler  will  recall
+       run  bundle  install, without any --without option, bundler will recall
        it.
 
-       Also,  calling  1mBundler.setup	22mwith  no  parameters, or calling 1mrequire0m
-       1m"bundler/setup" 22mwill setup all groups except for the ones you  excluded
-       via 1m--without 22m(since they are not available).
+       Also, calling Bundler.setup with  no  parameters,  or  calling  require
+       "bundler/setup"	will setup all groups except for the ones you excluded
+       via --without (since they are not available).
 
-       Note  that on 1mbundle install22m, bundler downloads and evaluates all gems,
-       in order to create a single canonical list of all of the required  gems
-       and  their dependencies. This means that you cannot list different ver-
-       sions of the same gems in  different  groups.  For  more  details,  see
-       Understanding Bundler 4mhttp://bundler.io/rationale.html24m.
+       Note that on bundle install, bundler downloads and evaluates all  gems,
+       in  order to create a single canonical list of all of the required gems
+       and their dependencies. This means that you cannot list different  ver-
+       sions  of  the  same  gems  in  different groups. For more details, see
+       Understanding Bundler http://bundler.io/rationale.html.
 
-   1mPLATFORMS0m
-       If  a  gem should only be used in a particular platform or set of plat-
-       forms, you can specify them. Platforms  are  essentially  identical  to
-       groups,	except	that you do not need to use the 1m--without 22minstall-time
+   PLATFORMS
+       If a gem should only be used in a particular platform or set  of  plat-
+       forms,  you  can  specify  them. Platforms are essentially identical to
+       groups, except that you do not need to use the  --without  install-time
        flag to exclude groups of gems for other platforms.
 
-       There are a number of 1mGemfile 22mplatforms:
+       There are a number of Gemfile platforms:
 
-       1mruby	22mC Ruby (MRI) or Rubinius, but 1mNOT 22mWindows
+       ruby   C Ruby (MRI) or Rubinius, but NOT Windows
 
-       1mmri	22mSame as 4mruby24m, but not Rubinius
+       mri    Same as ruby, but not Rubinius
 
-       1mmingw	22mWindows 32 bit 'mingw32' platform (aka RubyInstaller)
+       mingw  Windows 32 bit 'mingw32' platform (aka RubyInstaller)
 
-       1mx64_mingw0m
+       x64_mingw
 	      Windows 64 bit 'mingw32' platform (aka RubyInstaller x64)
 
-       1mrbx	22mSame as 4mruby24m, but only Rubinius (not MRI)
+       rbx    Same as ruby, but only Rubinius (not MRI)
 
-       1mjruby	22mJRuby
+       jruby  JRuby
 
-       1mmswin	22mWindows
+       mswin  Windows
 
-       You can restrict further by platform  and  version  for	all  platforms
-       4mexcept24m for 1mrbx22m, 1mjruby22m, and 1mmswin22m.
+       You  can  restrict  further  by	platform and version for all platforms
+       except for rbx, jruby, and mswin.
 
        To specify a version in addition to a platform, append the version num-
        ber without the delimiter to the platform. For example, to specify that
@@ -267,13 +267,13 @@ GEMFILE(5)							    GEMFILE(5)
 
        The full list of platforms and supported versions includes:
 
-       1mruby	22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+       ruby   1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
-       1mmri	22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+       mri    1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
-       1mmingw	22m1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
+       mingw  1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
-       1mx64_mingw0m
+       x64_mingw
 	      2.0, 2.1, 2.2, 2.3, 2.4, 2.5
 
        As with groups, you can specify one or more platforms:
@@ -286,12 +286,12 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       All   operations   involving  groups  (1mbundle	install22m,  1mBundler.setup22m,
-       1mBundler.require22m) behave exactly the same as if any groups not  matching
+       All  operations	involving  groups  (bundle   install,	Bundler.setup,
+       Bundler.require)  behave exactly the same as if any groups not matching
        the current platform were explicitly excluded.
 
-   1mSOURCE0m
-       You  can  select  an  alternate Rubygems repository for a gem using the
+   SOURCE
+       You can select an alternate Rubygems repository for  a  gem  using  the
        ':source' option.
 
 
@@ -300,54 +300,54 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       This forces the gem to be loaded  from  this  source  and  ignores  any
-       global  sources	declared at the top level of the file. If the gem does
+       This  forces  the  gem  to  be  loaded from this source and ignores any
+       global sources declared at the top level of the file. If the  gem  does
        not exist in this source, it will not be installed.
 
        Bundler will search for child dependencies of this gem by first looking
        in the source selected for the parent, but if they are not found there,
-       it will fall back on global sources using  the  ordering  described  in
-       4mSOURCE24m 4mPRIORITY24m.
+       it  will  fall  back  on global sources using the ordering described in
+       SOURCE PRIORITY.
 
-       Selecting  a  specific  source  repository this way also suppresses the
-       ambiguous gem warning described above in 4mGLOBAL24m 4mSOURCES24m 4m(#source)24m.
+       Selecting a specific source repository this  way  also  suppresses  the
+       ambiguous gem warning described above in GLOBAL SOURCES (#source).
 
-   1mGIT0m
+   GIT
        If necessary, you can specify that a gem is located at a particular git
-       repository using the 1m:git 22mparameter. The repository can be accessed via
+       repository using the :git parameter. The repository can be accessed via
        several protocols:
 
-       1mHTTP(S)0m
+       HTTP(S)
 	      gem "rails", :git => "https://github.com/rails/rails.git"
 
-       1mSSH	22mgem "rails", :git => "git@github.com:rails/rails.git"
+       SSH    gem "rails", :git => "git@github.com:rails/rails.git"
 
-       1mgit	22mgem "rails", :git => "git://github.com/rails/rails.git"
+       git    gem "rails", :git => "git://github.com/rails/rails.git"
 
-       If using SSH, the user that you use to run 1mbundle install MUST 22mhave the
-       appropriate keys available in their 1m$HOME/.ssh22m.
+       If using SSH, the user that you use to run bundle install MUST have the
+       appropriate keys available in their $HOME/.ssh.
 
-       1mNOTE22m:  1mhttp://  22mand  1mgit://	22mURLs should be avoided if at all possible.
-       These protocols are unauthenticated, so	a  man-in-the-middle  attacker
-       can  deliver  malicious	code and compromise your system. HTTPS and SSH
+       NOTE: http:// and git:// URLs should be avoided	if  at	all  possible.
+       These  protocols  are  unauthenticated, so a man-in-the-middle attacker
+       can deliver malicious code and compromise your system.  HTTPS  and  SSH
        are strongly preferred.
 
-       The 1mgroup22m, 1mplatforms22m, and 1mrequire  22moptions  are  available  and  behave
+       The  group,  platforms,	and  require  options are available and behave
        exactly the same as they would for a normal gem.
 
-       A  git  repository  1mSHOULD  22mhave  at least one file, at the root of the
-       directory containing the gem, with the extension  1m.gemspec22m.  This  file
-       1mMUST  22mcontain  a  valid gem specification, as expected by the 1mgem build0m
+       A git repository SHOULD have at least one file,	at  the  root  of  the
+       directory  containing  the  gem, with the extension .gemspec. This file
+       MUST contain a valid gem specification, as expected by  the  gem  build
        command.
 
-       If a git repository does not have a 1m.gemspec22m, bundler will	attempt  to
+       If  a  git repository does not have a .gemspec, bundler will attempt to
        create one, but it will not contain any dependencies, executables, or C
-       extension compilation instructions. As a result, it may fail  to  prop-
+       extension  compilation  instructions. As a result, it may fail to prop-
        erly integrate into your application.
 
-       If  a  git  repository does have a 1m.gemspec 22mfor the gem you attached it
-       to, a version specifier, if provided, means that the git repository  is
-       only  valid  if	the  1m.gemspec 22mspecifies a version matching the version
+       If a git repository does have a .gemspec for the gem  you  attached  it
+       to,  a version specifier, if provided, means that the git repository is
+       only valid if the .gemspec specifies a  version	matching  the  version
        specifier. If not, bundler will print a warning.
 
 
@@ -358,35 +358,35 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       If a git repository does 1mnot 22mhave a 1m.gemspec 22mfor the gem  you	attached
-       it to, a version specifier 1mMUST 22mbe provided. Bundler will use this ver-
-       sion in the simple 1m.gemspec 22mit creates.
+       If  a  git repository does not have a .gemspec for the gem you attached
+       it to, a version specifier MUST be provided. Bundler will use this ver-
+       sion in the simple .gemspec it creates.
 
        Git repositories support a number of additional options.
 
-       1mbranch22m, 1mtag22m, and 1mref0m
-	      You 1mMUST 22monly specify at most one of these options. The  default
-	      is 1m:branch => "master"0m
+       branch, tag, and ref
+	      You  MUST only specify at most one of these options. The default
+	      is :branch => "master"
 
        For example:
 
-	      git  "https://github.com/rails/rails.git",  :branch => "5-0-sta-
+	      git "https://github.com/rails/rails.git", :branch  =>  "5-0-sta-
 	      ble" do
 
 	      git "https://github.com/rails/rails.git", :tag => "v5.0.0" do
 
 	      git "https://github.com/rails/rails.git", :ref => "4aded" do
 
-       1msubmodules0m
-	      For	  reference,	     a		git	     submodule
-	      4mhttps://git-scm.com/book/en/v2/Git-Tools-Submodules24m	 lets	you
-	      have another git repository within a subfolder of  your  reposi-
-	      tory. Specify 1m:submodules => true 22mto cause bundler to expand any
+       submodules
+	      For	   reference,	       a	 git	     submodule
+	      https://git-scm.com/book/en/v2/Git-Tools-Submodules   lets   you
+	      have  another  git repository within a subfolder of your reposi-
+	      tory. Specify :submodules => true to cause bundler to expand any
 	      submodules included in the git repository
 
-       If a git repository contains multiple 1m.gemspecs22m, each  1m.gemspec  22mrepre-
-       sents  a  gem located at the same place in the file system as the 1m.gem-0m
-       1mspec22m.
+       If  a  git repository contains multiple .gemspecs, each .gemspec repre-
+       sents a gem located at the same place in the file system as  the  .gem-
+       spec.
 
 
 
@@ -400,16 +400,16 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       To install a gem located in a git repository, bundler  changes  to  the
-       directory  containing the gemspec, runs 1mgem build name.gemspec 22mand then
-       installs the resulting gem. The 1mgem build 22mcommand, which comes standard
-       with  Rubygems,	evaluates the 1m.gemspec 22min the context of the directory
+       To  install  a  gem located in a git repository, bundler changes to the
+       directory containing the gemspec, runs gem build name.gemspec and  then
+       installs the resulting gem. The gem build command, which comes standard
+       with Rubygems, evaluates the .gemspec in the context of	the  directory
        in which it is located.
 
-   1mGIT SOURCE0m
-       A custom git source can be defined via the 1mgit_source	22mmethod.  Provide
-       the  source's  name as an argument, and a block which receives a single
-       argument and interpolates it into a string  to  return  the  full  repo
+   GIT SOURCE
+       A  custom  git source can be defined via the git_source method. Provide
+       the source's name as an argument, and a block which receives  a	single
+       argument  and  interpolates  it	into  a string to return the full repo
        address:
 
 
@@ -427,15 +427,15 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-   1mGITHUB0m
-       1mNOTE22m: This shorthand should be avoided until Bundler 2.0, since it cur-
-       rently expands to an insecure 1mgit:// 22mURL. This allows a man-in-the-mid-
+   GITHUB
+       NOTE: This shorthand should be avoided until Bundler 2.0, since it cur-
+       rently expands to an insecure git:// URL. This allows a man-in-the-mid-
        dle attacker to compromise your system.
 
-       If  the	git repository you want to use is hosted on GitHub and is pub-
-       lic, you can use the :github shorthand to specify the  github  username
-       and  repository	name  (without	the  trailing  ".git"), separated by a
-       slash. If both the username and repository name are the same,  you  can
+       If the git repository you want to use is hosted on GitHub and  is  pub-
+       lic,  you  can use the :github shorthand to specify the github username
+       and repository name (without  the  trailing  ".git"),  separated  by  a
+       slash.  If  both the username and repository name are the same, you can
        omit one.
 
 
@@ -453,12 +453,12 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       Since the 1mgithub 22mmethod is a specialization of 1mgit_source22m, it accepts a
-       1m:branch 22mnamed argument.
+       Since the github method is a specialization of git_source, it accepts a
+       :branch named argument.
 
-   1mGIST0m
+   GIST
        If the git repository you want to use is hosted as a Github Gist and is
-       public,	you can use the :gist shorthand to specify the gist identifier
+       public, you can use the :gist shorthand to specify the gist  identifier
        (without the trailing ".git").
 
 
@@ -475,14 +475,14 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       Since the 1mgist 22mmethod is a specialization of 1mgit_source22m, it  accepts  a
-       1m:branch 22mnamed argument.
+       Since  the  gist method is a specialization of git_source, it accepts a
+       :branch named argument.
 
-   1mBITBUCKET0m
-       If  the	git  repository  you want to use is hosted on Bitbucket and is
-       public, you can use the :bitbucket shorthand to specify	the  bitbucket
-       username  and  repository name (without the trailing ".git"), separated
-       by a slash. If both the username and repository name are the same,  you
+   BITBUCKET
+       If the git repository you want to use is hosted	on  Bitbucket  and  is
+       public,	you  can use the :bitbucket shorthand to specify the bitbucket
+       username and repository name (without the trailing  ".git"),  separated
+       by  a slash. If both the username and repository name are the same, you
        can omit one.
 
 
@@ -500,19 +500,19 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-       Since  the  1mbitbucket	22mmethod  is  a  specialization  of 1mgit_source22m, it
-       accepts a 1m:branch 22mnamed argument.
+       Since the bitbucket  method  is	a  specialization  of  git_source,  it
+       accepts a :branch named argument.
 
-   1mPATH0m
-       You can specify that a gem is located in a particular location  on  the
+   PATH
+       You  can  specify that a gem is located in a particular location on the
        file system. Relative paths are resolved relative to the directory con-
-       taining the 1mGemfile22m.
+       taining the Gemfile.
 
-       Similar to the semantics of the 1m:git 22moption, the 1m:path 22moption	requires
-       that  the directory in question either contains a 1m.gemspec 22mfor the gem,
+       Similar	to the semantics of the :git option, the :path option requires
+       that the directory in question either contains a .gemspec for the  gem,
        or that you specify an explicit version that bundler should use.
 
-       Unlike 1m:git22m, bundler does not compile C extensions for  gems  specified
+       Unlike  :git,  bundler does not compile C extensions for gems specified
        as paths.
 
 
@@ -522,8 +522,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        If you would like to use multiple local gems directly from the filesys-
-       tem, you can set a global 1mpath 22moption to the path containing the  gem's
-       files. This will automatically load gemspec files from subdirectories.
+       tem,  you can set a global path option to the path containing the gem's
+       files. This will automatically load gemspec files from  subdirectories.
 
 
 
@@ -534,8 +534,8 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mBLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS0m
-       The 1m:source22m, 1m:git22m, 1m:path22m, 1m:group22m, and 1m:platforms 22moptions may be applied
+BLOCK FORM OF SOURCE, GIT, PATH, GROUP and PLATFORMS
+       The :source, :git, :path, :group, and :platforms options may be applied
        to a group of gems by using block form.
 
 
@@ -563,15 +563,15 @@ GEMFILE(5)							    GEMFILE(5)
 
 
        In the case of the group block form the :optional option can  be  given
-       to  prevent  a  group  from being installed unless listed in the 1m--with0m
-       option given to the 1mbundle install 22mcommand.
+       to  prevent  a  group  from being installed unless listed in the --with
+       option given to the bundle install command.
 
-       In the case of the 1mgit 22mblock form, the 1m:ref22m, 1m:branch22m, 1m:tag22m,	and  1m:sub-0m
-       1mmodules  22moptions  may  be passed to the 1mgit 22mmethod, and all gems in the
+       In the case of the git block form, the :ref, :branch, :tag,  and  :sub-
+       modules	options  may  be passed to the git method, and all gems in the
        block will inherit those options.
 
-1mINSTALL_IF0m
-       The 1minstall_if 22mmethod allows gems to be installed based on	a  proc  or
+INSTALL_IF
+       The install_if method allows gems to be installed based on  a  proc  or
        lambda.	This  is  especially useful for optional gems that can only be
        used if certain software is installed or some other conditions are met.
 
@@ -583,54 +583,54 @@ GEMFILE(5)							    GEMFILE(5)
 
 
 
-1mGEMSPEC0m
-       The .gemspec  4mhttp://guides.rubygems.org/specification-reference/24m  file
+GEMSPEC
+       The  .gemspec  http://guides.rubygems.org/specification-reference/ file
        is where you provide metadata about your gem to Rubygems. Some required
-       Gemspec attributes include the name, description, and homepage of  your
-       gem.  This is also where you specify the dependencies your gem needs to
+       Gemspec	attributes include the name, description, and homepage of your
+       gem. This is also where you specify the dependencies your gem needs  to
        run.
 
        If you wish to use Bundler to help install dependencies for a gem while
-       it  is being developed, use the 1mgemspec 22mmethod to pull in the dependen-
-       cies listed in the 1m.gemspec 22mfile.
+       it is being developed, use the gemspec method to pull in the  dependen-
+       cies listed in the .gemspec file.
 
-       The 1mgemspec 22mmethod adds any runtime dependencies as gem requirements in
-       the  default  group.  It  also  adds  development  dependencies	as gem
-       requirements in the 1mdevelopment 22mgroup. Finally, it adds a gem  require-
-       ment on your project (1m:path => '.'22m). In conjunction with 1mBundler.setup22m,
+       The gemspec method adds any runtime dependencies as gem requirements in
+       the default  group.  It	also  adds  development  dependencies  as  gem
+       requirements  in the development group. Finally, it adds a gem require-
+       ment on your project (:path => '.'). In conjunction with Bundler.setup,
        this allows you to require project files in your test code as you would
-       if  the	project  were  installed as a gem; you need not manipulate the
+       if the project were installed as a gem; you  need  not  manipulate  the
        load path manually or require project files via relative paths.
 
-       The 1mgemspec 22mmethod supports optional 1m:path22m, 1m:glob22m, 1m:name22m, and 1m:develop-0m
-       1mment_group 22moptions, which control where bundler looks for the 1m.gemspec22m,
-       the glob it uses to look for the  gemspec  (defaults  to:  "{,4m,24m/*}.gem-
-       spec"),	what named 1m.gemspec 22mit uses (if more than one is present), and
+       The gemspec method supports optional :path, :glob, :name, and :develop-
+       ment_group options, which control where bundler looks for the .gemspec,
+       the  glob  it  uses  to look for the gemspec (defaults to: "{,,/*}.gem-
+       spec"), what named .gemspec it uses (if more than one is present),  and
        which group development dependencies are included in.
 
-       When a 1mgemspec 22mdependency encounters version conflicts  during  resolu-
-       tion,  the  local  version under development will always be selected --
-       even if there are remote versions that better match other  requirements
-       for the 1mgemspec 22mgem.
+       When  a	gemspec dependency encounters version conflicts during resolu-
+       tion, the local version under development will always  be  selected  --
+       even  if there are remote versions that better match other requirements
+       for the gemspec gem.
 
-1mSOURCE PRIORITY0m
-       When  attempting  to locate a gem to satisfy a gem requirement, bundler
+SOURCE PRIORITY
+       When attempting to locate a gem to satisfy a gem  requirement,  bundler
        uses the following priority order:
 
-       1.  The source explicitly attached to the gem (using 1m:source22m, 1m:path22m, or
-	   1m:git22m)
+       1.  The source explicitly attached to the gem (using :source, :path, or
+	   :git)
 
        2.  For implicit gems (dependencies of explicit gems), any source, git,
-	   or path repository declared on the parent. This results in  bundler
-	   prioritizing  the  ActiveSupport  gem from the Rails git repository
-	   over ones from 1mrubygems.org0m
+	   or  path repository declared on the parent. This results in bundler
+	   prioritizing the ActiveSupport gem from the	Rails  git  repository
+	   over ones from rubygems.org
 
-       3.  The sources specified  via  global  1msource  22mlines,  searching  each
-	   source in your 1mGemfile 22mfrom last added to first added.
+       3.  The	sources  specified  via  global  source  lines, searching each
+	   source in your Gemfile from last added to first added.
 
 
 
 
 
 
-				 October 2017			    GEMFILE(5)
+				   July 2017			    GEMFILE(5)