bundler 1.15.1 → 1.17.3

data/man/bundle-exec.1.txt

@@ -2,53 +2,53 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
 
 
-1mNAME0m
-       1mbundle-exec 22m- Execute a command in the context of the bundle
+NAME
+       bundle-exec - Execute a command in the context of the bundle
 
-1mSYNOPSIS0m
-       1mbundle exec 22m[--keep-file-descriptors] 4mcommand0m
+SYNOPSIS
+       bundle exec [--keep-file-descriptors] command
 
-1mDESCRIPTION0m
+DESCRIPTION
        This  command  executes	the  command, making all gems specified in the
-       1mGemfile(5) 22mavailable to 1mrequire 22min Ruby programs.
+       [Gemfile(5)][Gemfile(5)] available to require in Ruby programs.
 
-       Essentially, if you  would  normally  have  run	something  like  1mrspec0m
-       1mspec/my_spec.rb22m,  and  you	want  to use the gems specified in the 1mGem-0m
-       1mfile(5) 22mand installed via bundle install(1) 4mbundle-install.1.html24m,  you
-       should run 1mbundle exec rspec spec/my_spec.rb22m.
+       Essentially, if you  would  normally  have  run	something  like  rspec
+       spec/my_spec.rb,  and  you  want to use the gems specified in the [Gem-
+       file(5)][Gemfile(5)]  and  installed   via   bundle   install(1)   bun-
+       dle-install.1.html, you should run bundle exec rspec spec/my_spec.rb.
 
-       Note  that 1mbundle exec 22mdoes not require that an executable is available
-       on your shell's 1m$PATH22m.
+       Note  that bundle exec does not require that an executable is available
+       on your shell's $PATH.
 
-1mOPTIONS0m
-       1m--keep-file-descriptors0m
+OPTIONS
+       --keep-file-descriptors
 	      Exec in Ruby 2.0 began discarding non-standard file descriptors.
 	      When  this flag is passed, exec will revert to the 1.9 behaviour
 	      of passing all file descriptors to the new process.
 
-1mBUNDLE INSTALL --BINSTUBS0m
-       If  you	use  the   1m--binstubs   22mflag   in	 bundle   install(1)   4mbun-0m
-       4mdle-install.1.html24m,  Bundler  will	automatically  create  a  directory
-       (which defaults to 1mapp_root/bin22m)  containing  all  of  the	executables
+BUNDLE INSTALL --BINSTUBS
+       If  you	use  the   --binstubs	flag   in   bundle   install(1)   bun-
+       dle-install.1.html,  Bundler  will  automatically  create  a  directory
+       (which defaults to app_root/bin)  containing  all  of  the  executables
        available from gems in the bundle.
 
-       After  using 1m--binstubs22m, 1mbin/rspec spec/my_spec.rb 22mis identical to 1mbun-0m
-       1mdle exec rspec spec/my_spec.rb22m.
+       After  using --binstubs, bin/rspec spec/my_spec.rb is identical to bun-
+       dle exec rspec spec/my_spec.rb.
 
-1mENVIRONMENT MODIFICATIONS0m
-       1mbundle exec 22mmakes a number of changes to the  shell  environment,  then
+ENVIRONMENT MODIFICATIONS
+       bundle exec makes a number of changes to the  shell  environment,  then
        executes the command you specify in full.
 
-       o   make  sure  that  it's  still  possible to shell out to 1mbundle 22mfrom
-	   inside a command invoked by 1mbundle exec 22m(using 1m$BUNDLE_BIN_PATH22m)
+       o   make  sure  that  it's  still  possible to shell out to bundle from
+	   inside a command invoked by bundle exec (using $BUNDLE_BIN_PATH)
 
-       o   put	the  directory	containing  executables  (like	1mrails22m,  1mrspec22m,
-	   1mrackup22m) for your bundle on 1m$PATH0m
+       o   put	the  directory	containing  executables  (like	rails,	rspec,
+	   rackup) for your bundle on $PATH
 
        o   make  sure  that if bundler is invoked in the subshell, it uses the
-	   same 1mGemfile 22m(by setting 1mBUNDLE_GEMFILE22m)
+	   same Gemfile (by setting BUNDLE_GEMFILE)
 
-       o   add 1m-rbundler/setup 22mto 1m$RUBYOPT22m, which makes sure	that  Ruby  pro-
+       o   add -rbundler/setup to $RUBYOPT, which makes sure  that  Ruby  pro-
 	   grams invoked in the subshell can see the gems in the bundle
 
 
@@ -57,35 +57,42 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
        o   disallow loading additional gems not in the bundle
 
-       o   modify  the 1mgem 22mmethod to be a no-op if a gem matching the require-
-	   ments is in the bundle, and to raise a 1mGem::LoadError 22mif it's not
+       o   modify  the gem method to be a no-op if a gem matching the require-
+	   ments is in the bundle, and to raise a Gem::LoadError if it's not
 
-       o   Define 1mGem.refresh 22mto be a no-op, since the source index is  always
+       o   Define Gem.refresh to be a no-op, since the source index is	always
 	   frozen  when  using	bundler,  and  to prevent gems from the system
 	   leaking into the environment
 
-       o   Override 1mGem.bin_path 22mto use the gems in the bundle, making  system
+       o   Override Gem.bin_path to use the gems in the bundle, making	system
 	   executables work
 
        o   Add all gems in the bundle into Gem.loaded_specs
 
 
 
-   1mLoading0m
-       By  default,  when attempting to 1mbundle exec 22mto a file with a ruby she-
-       bang, Bundler will 1mKernel.load 22mthat file instead of using  1mKernel.exec22m.
+       Finally, bundle exec also implicitly modifies Gemfile.lock if the lock-
+       file and the Gemfile do not match. Bundler needs the Gemfile to	deter-
+       mine  things  such as a gem's groups, autorequire, and platforms, etc.,
+       and that information isn't stored in  the  lockfile.  The  Gemfile  and
+       lockfile must be synced in order to bundle exec successfully, so bundle
+       exec updates the lockfile beforehand.
+
+   Loading
+       By default, when attempting to bundle exec to a file with a  ruby  she-
+       bang,  Bundler will Kernel.load that file instead of using Kernel.exec.
        For the vast majority of cases, this is a performance improvement. In a
-       rare few cases, this could cause  some  subtle  side-effects  (such  as
-       dependence  on  the exact contents of 1m$0 22mor 1m__FILE__22m) and the optimiza-
-       tion can be disabled by enabling the 1mdisable_exec_load 22msetting.
-
-   1mShelling out0m
-       Any Ruby code that opens a subshell (like 1msystem22m, backticks,  or  1m%x{}22m)
-       will  automatically use the current Bundler environment. If you need to
-       shell out to a Ruby command that is not part of	your  current  bundle,
-       use  the  1mwith_clean_env  22mmethod  with  a  block. Any subshells created
-       inside the block will be given the environment present  before  Bundler
-       was  activated. For example, Homebrew commands run Ruby, but don't work
+       rare  few  cases,  this	could  cause some subtle side-effects (such as
+       dependence on the exact contents of $0 or __FILE__) and	the  optimiza-
+       tion can be disabled by enabling the disable_exec_load setting.
+
+   Shelling out
+       Any  Ruby  code that opens a subshell (like system, backticks, or %x{})
+       will automatically use the current Bundler environment. If you need  to
+       shell  out  to  a Ruby command that is not part of your current bundle,
+       use the with_clean_env method  with  a  block.  Any  subshells  created
+       inside  the  block will be given the environment present before Bundler
+       was activated. For example, Homebrew commands run Ruby, but don't  work
        inside a bundle:
 
 
@@ -96,10 +103,10 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
 
 
-       Using 1mwith_clean_env 22mis also necessary if you are  shelling  out  to  a
-       different  bundle.  Any Bundler commands run in a subshell will inherit
-       the current Gemfile, so commands that need to run in the context  of  a
-       different bundle also need to use 1mwith_clean_env22m.
+       Using  with_clean_env  is  also	necessary if you are shelling out to a
+       different bundle. Any Bundler commands run in a subshell  will  inherit
+       the  current  Gemfile, so commands that need to run in the context of a
+       different bundle also need to use with_clean_env.
 
 
 
@@ -111,7 +118,7 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
 
 
-       Bundler	provides  convenience  helpers	that wrap 1msystem 22mand 1mexec22m, and
+       Bundler provides convenience helpers that wrap  system  and  exec,  and
        they can be used like this:
 
 
@@ -121,24 +128,24 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
 
 
-1mRUBYGEMS PLUGINS0m
-       At present,  the  Rubygems  plugin  system  requires  all  files  named
-       1mrubygems_plugin.rb  22mon the load path of 4many24m installed gem when any Ruby
-       code requires 1mrubygems.rb22m. This includes executables installed into the
-       system, like 1mrails22m, 1mrackup22m, and 1mrspec22m.
+RUBYGEMS PLUGINS
+       At  present,  the  Rubygems  plugin  system  requires  all  files named
+       rubygems_plugin.rb on the load path of any installed gem when any  Ruby
+       code requires rubygems.rb. This includes executables installed into the
+       system, like rails, rackup, and rspec.
 
-       Since  Rubygems	plugins can contain arbitrary Ruby code, they commonly
+       Since Rubygems plugins can contain arbitrary Ruby code,	they  commonly
        end up activating themselves or their dependencies.
 
-       For instance, the 1mgemcutter 0.5 22mgem depended on 1mjson_pure22m. If	you  had
-       that  version of gemcutter installed (even if you 4malso24m had a newer ver-
-       sion without this problem), Rubygems would activate 1mgemcutter	0.5  22mand
-       1mjson_pure <latest>22m.
+       For  instance,  the gemcutter 0.5 gem depended on json_pure. If you had
+       that version of gemcutter installed (even if you also had a newer  ver-
+       sion  without  this problem), Rubygems would activate gemcutter 0.5 and
+       json_pure <latest>.
 
-       If your Gemfile(5) also contained 1mjson_pure 22m(or a gem with a dependency
-       on 1mjson_pure22m), the latest version on your system  might  conflict  with
-       the  version  in  your Gemfile(5), or the snapshot version in your 1mGem-0m
-       1mfile.lock22m.
+       If your Gemfile(5) also contained json_pure (or a gem with a dependency
+       on  json_pure),	the  latest version on your system might conflict with
+       the version in your Gemfile(5), or the snapshot version	in  your  Gem-
+       file.lock.
 
        If this happens, bundler will say:
 
@@ -149,9 +156,9 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
 
 
-       In this situation, you almost certainly want to remove  the  underlying
-       gem  with  the problematic gem plugin. In general, the authors of these
-       plugins (in this case, the 1mgemcutter 22mgem) have released newer  versions
+       In  this  situation, you almost certainly want to remove the underlying
+       gem with the problematic gem plugin. In general, the authors  of  these
+       plugins	(in this case, the gemcutter gem) have released newer versions
        that are more careful in their plugins.
 
        You can find a list of all the gems containing gem plugins by running
@@ -163,9 +170,9 @@ BUNDLE-EXEC(1)							BUNDLE-EXEC(1)
 
 
        At the very least, you should remove all but the newest version of each
-       gem plugin, and also remove all gem plugins that you aren't using  (1mgem0m
-       1muninstall gem_name22m).
+       gem  plugin, and also remove all gem plugins that you aren't using (gem
+       uninstall gem_name).
 
 
 
-				   May 2017			BUNDLE-EXEC(1)
+				 November 2018			BUNDLE-EXEC(1)

data/man/bundle-exec.ronn

@@ -8,11 +8,11 @@ bundle-exec(1) -- Execute a command in the context of the bundle
 ## DESCRIPTION
 
 This command executes the command, making all gems specified in the
-`Gemfile(5)` available to `require` in Ruby programs.
+[`Gemfile(5)`][Gemfile(5)] available to `require` in Ruby programs.
 
 Essentially, if you would normally have run something like
 `rspec spec/my_spec.rb`, and you want to use the gems specified
-in the `Gemfile(5)` and installed via [bundle install(1)][bundle-install], you
+in the [`Gemfile(5)`][Gemfile(5)] and installed via [bundle install(1)](bundle-install.1.html), you
 should run `bundle exec rspec spec/my_spec.rb`.
 
 Note that `bundle exec` does not require that an executable is
@@ -27,7 +27,7 @@ available on your shell's `$PATH`.
 
 ## BUNDLE INSTALL --BINSTUBS
 
-If you use the `--binstubs` flag in [bundle install(1)][bundle-install], Bundler will
+If you use the `--binstubs` flag in [bundle install(1)](bundle-install.1.html), Bundler will
 automatically create a directory (which defaults to `app_root/bin`)
 containing all of the executables available from gems in the bundle.
 
@@ -63,6 +63,13 @@ It also modifies Rubygems:
   making system executables work
 * Add all gems in the bundle into Gem.loaded_specs
 
+Finally, `bundle exec` also implicitly modifies `Gemfile.lock` if the lockfile
+and the Gemfile do not match. Bundler needs the Gemfile to determine things
+such as a gem's groups, `autorequire`, and platforms, etc., and that
+information isn't stored in the lockfile. The Gemfile and lockfile must be
+synced in order to `bundle exec` successfully, so `bundle exec`
+updates the lockfile beforehand.
+
 ### Loading
 
 By default, when attempting to `bundle exec` to a file with a ruby shebang,

data/man/bundle-gem.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-GEM" "1" "November 2016" "" ""
+.TH "BUNDLE\-GEM" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-gem\fR \- Generate a project skeleton for creating a rubygem
@@ -13,7 +13,7 @@
 Generates a directory named \fBGEM_NAME\fR with a \fBRakefile\fR, \fBGEM_NAME\.gemspec\fR, and other supporting files and directories that can be used to develop a rubygem with that name\.
 .
 .P
-Run \fBrake \-T\fR in the resulting project for a list of Rake tasks that can used to test and publish the gem to rubygems\.org\.
+Run \fBrake \-T\fR in the resulting project for a list of Rake tasks that can be used to test and publish the gem to rubygems\.org\.
 .
 .P
 The generated project skeleton can be customized with OPTIONS, as explained below\. Note that these options can also be specified via Bundler\'s global configuration file using the following names:
@@ -65,7 +65,7 @@ Do not create a \fBLICENSE\.txt\fR (overrides \fB\-\-mit\fR specified in the glo
 .
 .TP
 \fB\-t\fR, \fB\-\-test=minitest\fR, \fB\-\-test=rspec\fR
-Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR and \fBrspec\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\.
+Specify the test framework that Bundler should use when generating the project\. Acceptable values are \fBminitest\fR and \fBrspec\fR\. The \fBGEM_NAME\.gemspec\fR will be configured and a skeleton test/spec directory will be created based on this option\. If this option is unspecified, an interactive prompt will be displayed and the answer will be saved in Bundler\'s global config for future \fBbundle gem\fR use\. If no option is specified, the default testing framework is RSpec\.
 .
 .TP
 \fB\-e\fR, \fB\-\-edit[=EDITOR]\fR
@@ -74,7 +74,7 @@ Open the resulting GEM_NAME\.gemspec in EDITOR, or the default editor if not spe
 .SH "SEE ALSO"
 .
 .IP "\(bu" 4
-bundle\-config(1)
+bundle config(1) \fIbundle\-config\.1\.html\fR
 .
 .IP "" 0
 

data/man/bundle-gem.1.txt

@@ -2,89 +2,90 @@ BUNDLE-GEM(1)							 BUNDLE-GEM(1)
 
 
 
-1mNAME0m
-       1mbundle-gem 22m- Generate a project skeleton for creating a rubygem
+NAME
+       bundle-gem - Generate a project skeleton for creating a rubygem
 
-1mSYNOPSIS0m
-       1mbundle gem 4m22mGEM_NAME24m 4mOPTIONS0m
+SYNOPSIS
+       bundle gem GEM_NAME OPTIONS
 
-1mDESCRIPTION0m
-       Generates a directory named 1mGEM_NAME 22mwith a 1mRakefile22m, 1mGEM_NAME.gemspec22m,
+DESCRIPTION
+       Generates a directory named GEM_NAME with a Rakefile, GEM_NAME.gemspec,
        and other supporting files and directories that can be used to  develop
        a rubygem with that name.
 
-       Run  1mrake -T 22min the resulting project for a list of Rake tasks that can
-       used to test and publish the gem to rubygems.org.
+       Run  rake -T in the resulting project for a list of Rake tasks that can
+       be used to test and publish the gem to rubygems.org.
 
        The generated project skeleton  can  be	customized  with  OPTIONS,  as
        explained  below.  Note	that  these  options can also be specified via
        Bundler's global configuration file using the following names:
 
-       o   1mgem.coc0m
+       o   gem.coc
 
-       o   1mgem.mit0m
+       o   gem.mit
 
-       o   1mgem.test0m
+       o   gem.test
 
 
 
-1mOPTIONS0m
-       1m--exe 22mor 1m-b 22mor 1m--bin0m
+OPTIONS
+       --exe or -b or --bin
 	      Specify that Bundler  should  create  a  binary  executable  (as
-	      1mexe/GEM_NAME22m) in the generated rubygem project. This binary will
-	      also be added to the 1mGEM_NAME.gemspec 22mmanifest. This behavior is
+	      exe/GEM_NAME) in the generated rubygem project. This binary will
+	      also be added to the GEM_NAME.gemspec manifest. This behavior is
 	      disabled by default.
 
-       1m--no-exe0m
-	      Do  not create a binary (overrides 1m--exe 22mspecified in the global
+       --no-exe
+	      Do  not create a binary (overrides --exe specified in the global
 	      config).
 
-       1m--coc	22mAdd a 1mCODE_OF_CONDUCT.md 22mfile  to  the	root  of  the  generated
+       --coc  Add a CODE_OF_CONDUCT.md file  to  the  root  of	the  generated
 	      project.	If  this  option is unspecified, an interactive prompt
 	      will be displayed and the answer	will  be  saved  in  Bundler's
-	      global config for future 1mbundle gem 22muse.
+	      global config for future bundle gem use.
 
-       1m--no-coc0m
-	      Do not create a 1mCODE_OF_CONDUCT.md 22m(overrides 1m--coc 22mspecified in
+       --no-coc
+	      Do not create a CODE_OF_CONDUCT.md (overrides --coc specified in
 	      the global config).
 
-       1m--ext	22mAdd boilerplate for C extension code to the	generated  project.
+       --ext  Add boilerplate for C extension code to the  generated  project.
 	      This behavior is disabled by default.
 
-       1m--no-ext0m
-	      Do  not  add  C extension code (overrides 1m--ext 22mspecified in the
+       --no-ext
+	      Do  not  add  C extension code (overrides --ext specified in the
 	      global config).
 
-       1m--mit	22mAdd an MIT license to a 1mLICENSE.txt 22mfile in the root of the gen-
+       --mit  Add an MIT license to a LICENSE.txt file in the root of the gen-
 	      erated project. Your name from the global git config is used for
 	      the copyright statement.	If  this  option  is  unspecified,  an
 	      interactive  prompt  will  be  displayed	and the answer will be
-	      saved in Bundler's global config for future 1mbundle gem 22muse.
+	      saved in Bundler's global config for future bundle gem use.
 
-       1m--no-mit0m
-	      Do not create a 1mLICENSE.txt 22m(overrides 1m--mit  22mspecified  in  the
+       --no-mit
+	      Do not create a LICENSE.txt (overrides --mit  specified  in  the
 	      global config).
 
-       1m-t22m, 1m--test=minitest22m, 1m--test=rspec0m
+       -t, --test=minitest, --test=rspec
 	      Specify the test framework that Bundler should use when generat-
-	      ing the project. Acceptable values are 1mminitest 22mand	1mrspec22m.  The
-	      1mGEM_NAME.gemspec  22mwill  be  configured  and a skeleton test/spec
+	      ing the project. Acceptable values are minitest and  rspec.  The
+	      GEM_NAME.gemspec	will  be  configured  and a skeleton test/spec
 	      directory will be created based on this option. If  this	option
 	      is  unspecified, an interactive prompt will be displayed and the
-	      answer will be saved in Bundler's global config for future  1mbun-0m
-	      1mdle gem 22muse.
+	      answer will be saved in Bundler's global config for future  bun-
+	      dle  gem	use.  If  no  option is specified, the default testing
+	      framework is RSpec.
 
-       1m-e22m, 1m--edit[=EDITOR]0m
-	      Open  the  resulting  GEM_NAME.gemspec in EDITOR, or the default
-	      editor if not specified. The default is  1m$BUNDLER_EDITOR22m,  1m$VIS-0m
-	      1mUAL22m, or 1m$EDITOR22m.
+       -e, --edit[=EDITOR]
+	      Open the resulting GEM_NAME.gemspec in EDITOR,  or  the  default
+	      editor   if  not	specified.  The  default  is  $BUNDLER_EDITOR,
+	      $VISUAL, or $EDITOR.
 
-1mSEE ALSO0m
-       o   bundle-config(1)
+SEE ALSO
+       o   bundle config(1) bundle-config.1.html
 
 
 
 
 
 
-				 November 2016			 BUNDLE-GEM(1)
+				 November 2018			 BUNDLE-GEM(1)

data/man/bundle-gem.ronn

@@ -11,7 +11,7 @@ Generates a directory named `GEM_NAME` with a `Rakefile`, `GEM_NAME.gemspec`,
 and other supporting files and directories that can be used to develop a
 rubygem with that name.
 
-Run `rake -T` in the resulting project for a list of Rake tasks that can used
+Run `rake -T` in the resulting project for a list of Rake tasks that can be used
 to test and publish the gem to rubygems.org.
 
 The generated project skeleton can be customized with OPTIONS, as explained
@@ -67,6 +67,7 @@ configuration file using the following names:
   on this option. If this option is unspecified, an interactive prompt will be
   displayed and the answer will be saved in Bundler's global config for future
   `bundle gem` use.
+  If no option is specified, the default testing framework is RSpec.
 
 * `-e`, `--edit[=EDITOR]`:
   Open the resulting GEM_NAME.gemspec in EDITOR, or the default editor if not
@@ -74,4 +75,4 @@ configuration file using the following names:
 
 ## SEE ALSO
 
-* bundle-config(1)
+* [bundle config(1)](bundle-config.1.html)

data/man/bundle-info.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INFO" "1" "May 2017" "" ""
+.TH "BUNDLE\-INFO" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-info\fR \- Show information for the given gem in your bundle

data/man/bundle-info.1.txt

@@ -2,20 +2,20 @@ BUNDLE-INFO(1)							BUNDLE-INFO(1)
 
 
 
-1mNAME0m
-       1mbundle-info 22m- Show information for the given gem in your bundle
+NAME
+       bundle-info - Show information for the given gem in your bundle
 
-1mSYNOPSIS0m
-       1mbundle info 22m[GEM] [--path]
+SYNOPSIS
+       bundle info [GEM] [--path]
 
-1mDESCRIPTION0m
+DESCRIPTION
        Print  the  basic  information about the provided GEM such as homepage,
        version, path and summary.
 
-1mOPTIONS0m
-       1m--path 22mPrint the path of the given gem
+OPTIONS
+       --path Print the path of the given gem
 
 
 
 
-				   May 2017			BUNDLE-INFO(1)
+				 November 2018			BUNDLE-INFO(1)

data/man/bundle-init.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INIT" "1" "May 2017" "" ""
+.TH "BUNDLE\-INIT" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-init\fR \- Generates a Gemfile into the current working directory
@@ -10,11 +10,16 @@
 \fBbundle init\fR [\-\-gemspec=FILE]
 .
 .SH "DESCRIPTION"
-Init generates a default \fBGemfile(5)\fR in the current working directory\. When adding a \fBGemfile(5)\fR to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created \fBGemfile(5)\fR\.
+Init generates a default [\fBGemfile(5)\fR][Gemfile(5)] in the current working directory\. When adding a [\fBGemfile(5)\fR][Gemfile(5)] to a gem with a gemspec, the \fB\-\-gemspec\fR option will automatically add each dependency listed in the gemspec file to the newly created [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .SH "OPTIONS"
 .
 .TP
 \fB\-\-gemspec\fR
-Use the specified \.gemspec to create the \fBGemfile(5)\fR
-
+Use the specified \.gemspec to create the [\fBGemfile(5)\fR][Gemfile(5)]
+.
+.SH "FILES"
+Included in the default [\fBGemfile(5)\fR][Gemfile(5)] generated is the line \fB# frozen_string_literal: true\fR\. This is a magic comment supported for the first time in Ruby 2\.3\. The presence of this line results in all string literals in the file being implicitly frozen\.
+.
+.SH "SEE ALSO"
+Gemfile(5) \fIhttp://bundler\.io/man/gemfile\.5\.html\fR

data/man/bundle-init.1.txt

@@ -2,23 +2,33 @@ BUNDLE-INIT(1)							BUNDLE-INIT(1)
 
 
 
-1mNAME0m
-       1mbundle-init 22m- Generates a Gemfile into the current working directory
+NAME
+       bundle-init - Generates a Gemfile into the current working directory
 
-1mSYNOPSIS0m
-       1mbundle init 22m[--gemspec=FILE]
+SYNOPSIS
+       bundle init [--gemspec=FILE]
 
-1mDESCRIPTION0m
-       Init  generates	a default 1mGemfile(5) 22min the current working directory.
-       When adding a 1mGemfile(5) 22mto a gem with a gemspec, the 1m--gemspec  22moption
-       will  automatically  add  each dependency listed in the gemspec file to
-       the newly created 1mGemfile(5)22m.
+DESCRIPTION
+       Init  generates a default [Gemfile(5)][Gemfile(5)] in the current work-
+       ing directory. When adding a [Gemfile(5)][Gemfile(5)] to a gem  with  a
+       gemspec,  the  --gemspec  option will automatically add each dependency
+       listed in the gemspec  file  to	the  newly  created  [Gemfile(5)][Gem-
+       file(5)].
 
-1mOPTIONS0m
-       1m--gemspec0m
-	      Use the specified .gemspec to create the 1mGemfile(5)0m
+OPTIONS
+       --gemspec
+	      Use  the	specified  .gemspec  to  create  the [Gemfile(5)][Gem-
+	      file(5)]
 
+FILES
+       Included in the default [Gemfile(5)][Gemfile(5)] generated is the  line
+       #  frozen_string_literal:  true.  This is a magic comment supported for
+       the first time in Ruby 2.3. The presence of this line  results  in  all
+       string literals in the file being implicitly frozen.
 
+SEE ALSO
+       Gemfile(5) http://bundler.io/man/gemfile.5.html
 
 
-				   May 2017			BUNDLE-INIT(1)
+
+				 November 2018			BUNDLE-INIT(1)

data/man/bundle-init.ronn

@@ -7,12 +7,23 @@ bundle-init(1) -- Generates a Gemfile into the current working directory
 
 ## DESCRIPTION
 
-Init generates a default `Gemfile(5)` in the current working directory. When
-adding a `Gemfile(5)` to a gem with a gemspec, the `--gemspec` option will
+Init generates a default [`Gemfile(5)`][Gemfile(5)] in the current working directory. When
+adding a [`Gemfile(5)`][Gemfile(5)] to a gem with a gemspec, the `--gemspec` option will
 automatically add each dependency listed in the gemspec file to the newly
-created `Gemfile(5)`.
+created [`Gemfile(5)`][Gemfile(5)].
 
 ## OPTIONS
 
 * `--gemspec`:
-  Use the specified .gemspec to create the `Gemfile(5)`
+  Use the specified .gemspec to create the [`Gemfile(5)`][Gemfile(5)]
+
+## FILES
+
+Included in the default [`Gemfile(5)`][Gemfile(5)]
+generated is the line `# frozen_string_literal: true`. This is a magic comment
+supported for the first time in Ruby 2.3. The presence of this line
+results in all string literals in the file being implicitly frozen.
+
+## SEE ALSO
+
+[Gemfile(5)](http://bundler.io/man/gemfile.5.html)

data/man/bundle-inject.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "BUNDLE\-INJECT" "1" "May 2017" "" ""
+.TH "BUNDLE\-INJECT" "1" "November 2018" "" ""
 .
 .SH "NAME"
 \fBbundle\-inject\fR \- Add named gem(s) with version requirements to Gemfile
@@ -10,10 +10,10 @@
 \fBbundle inject\fR [GEM] [VERSION]
 .
 .SH "DESCRIPTION"
-Adds the named gem(s) with their version requirements to the resolved \fBGemfile(5)\fR\.
+Adds the named gem(s) with their version requirements to the resolved [\fBGemfile(5)\fR][Gemfile(5)]\.
 .
 .P
-This command will add the gem to both your \fBGemfile(5)\fR and Gemfile\.lock if it isn\'t listed yet\.
+This command will add the gem to both your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock if it isn\'t listed yet\.
 .
 .P
 Example:
@@ -30,4 +30,4 @@ bundle inject \'rack\' \'> 0\'
 .IP "" 0
 .
 .P
-This will inject the \'rack\' gem with a version greater than 0 in your \fBGemfile(5)\fR and Gemfile\.lock
+This will inject the \'rack\' gem with a version greater than 0 in your [\fBGemfile(5)\fR][Gemfile(5)] and Gemfile\.lock