lib/bundler/man/bundle-gem.txt in bundler-1.13.4 vs lib/bundler/man/bundle-gem.txt in bundler-1.13.5
- old
+ new
@@ -1,86 +1,86 @@
BUNDLE-GEM(1) BUNDLE-GEM(1)
-NAME
- bundle-gem - Generate a project skeleton for creating a rubygem
+1mNAME0m
+ 1mbundle-gem 22m- Generate a project skeleton for creating a rubygem
-SYNOPSIS
- bundle gem GEM_NAME OPTIONS
+1mSYNOPSIS0m
+ 1mbundle gem 4m22mGEM_NAME24m 4mOPTIONS0m
-DESCRIPTION
- Generates a directory named GEM_NAME with a Rakefile, GEM_NAME.gemspec,
+1mDESCRIPTION0m
+ Generates a directory named 1mGEM_NAME 22mwith a 1mRakefile22m, 1mGEM_NAME.gemspec22m,
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
+ 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.
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 gem.coc
+ o 1mgem.coc0m
- o gem.mit
+ o 1mgem.mit0m
- o gem.test
+ o 1mgem.test0m
-OPTIONS
- --exe or -b or --bin
+1mOPTIONS0m
+ 1m--exe 22mor 1m-b 22mor 1m--bin0m
Specify that Bundler should create a binary executable (as
- exe/GEM_NAME) in the generated rubygem project. This binary will
- also be added to the GEM_NAME.gemspec manifest. This behavior is
+ 1mexe/GEM_NAME22m) in the generated rubygem project. This binary will
+ also be added to the 1mGEM_NAME.gemspec 22mmanifest. This behavior is
disabled by default.
- --no-exe
- Do not create a binary (overrides --exe specified in the global
+ 1m--no-exe0m
+ Do not create a binary (overrides 1m--exe 22mspecified in the global
config).
- --coc Add a CODE_OF_CONDUCT.md file to the root of the generated
+ 1m--coc 22mAdd a 1mCODE_OF_CONDUCT.md 22mfile 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 bundle gem use.
+ global config for future 1mbundle gem 22muse.
- --no-coc
- Do not create a CODE_OF_CONDUCT.md (overrides --coc specified in
+ 1m--no-coc0m
+ Do not create a 1mCODE_OF_CONDUCT.md 22m(overrides 1m--coc 22mspecified in
the global config).
- --ext Add boilerplate for C extension code to the generated project.
+ 1m--ext 22mAdd boilerplate for C extension code to the generated project.
This behavior is disabled by default.
- --no-ext
- Do not add C extension code (overrides --ext specified in the
+ 1m--no-ext0m
+ Do not add C extension code (overrides 1m--ext 22mspecified in the
global config).
- --mit Add an MIT license to a LICENSE.txt file in the root of the gen-
+ 1m--mit 22mAdd an MIT license to a 1mLICENSE.txt 22mfile 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 bundle gem use.
+ saved in Bundler's global config for future 1mbundle gem 22muse.
- --no-mit
- Do not create a LICENSE.txt (overrides --mit specified in the
+ 1m--no-mit0m
+ Do not create a 1mLICENSE.txt 22m(overrides 1m--mit 22mspecified in the
global config).
- -t, --test=minitest, --test=rspec
+ 1m-t22m, 1m--test=minitest22m, 1m--test=rspec0m
Specify the test framework that Bundler should use when generat-
- ing the project. Acceptable values are minitest and rspec. The
- GEM_NAME.gemspec will be configured and a skeleton test/spec
+ ing the project. Acceptable values are 1mminitest 22mand 1mrspec22m. The
+ 1mGEM_NAME.gemspec 22mwill 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 bun-
- dle gem use.
+ answer will be saved in Bundler's global config for future 1mbun-0m
+ 1mdle gem 22muse.
- -e, --edit[=EDITOR]
+ 1m-e22m, 1m--edit[=EDITOR]0m
Open the resulting GEM_NAME.gemspec in EDITOR, or the default
- editor if not specified. The default is $BUNDLER_EDITOR,
- $VISUAL, or $EDITOR.
+ editor if not specified. The default is 1m$BUNDLER_EDITOR22m, 1m$VIS-0m
+ 1mUAL22m, or 1m$EDITOR22m.
-SEE ALSO
+1mSEE ALSO0m
o bundle-config(1)