summaryrefslogtreecommitdiff
path: root/man/gemfile.5.ronn
diff options
context:
space:
mode:
authorHiro Asari <asari.ruby@gmail.com>2018-05-17 21:52:08 -0400
committerHiro Asari <asari.ruby@gmail.com>2018-05-17 22:06:57 -0400
commit2e7a0ea035a12cf5dfc6664058e1490f94b3d819 (patch)
treee5b316d4a4dc42cadbf29340b8fc06abeadca4a6 /man/gemfile.5.ronn
parent0c5d3b8c1f391aa5175321675ecd91ee6a1f231b (diff)
downloadbundler-2e7a0ea035a12cf5dfc6664058e1490f94b3d819.tar.gz
Fix man page links
With markup [`bundle platform(1)`][bundle-platform(1)] ronn creates this HTML fragment <dt><a href="bundle-platform.html"><code>bundle platform(1)</code></a></dt><dd><p>Display platform compatibility information</p></dd> At the same time, it generates HTML file `bundle-platform.1.html` based on the man page section, and this results in certain inter-man-page links 404. We resolve this inconsistency by spelling out the href attributes.
Diffstat (limited to 'man/gemfile.5.ronn')
-rw-r--r--man/gemfile.5.ronn4
1 files changed, 2 insertions, 2 deletions
diff --git a/man/gemfile.5.ronn b/man/gemfile.5.ronn
index 9f6bbce93a..5c7ba23b29 100644
--- a/man/gemfile.5.ronn
+++ b/man/gemfile.5.ronn
@@ -35,7 +35,7 @@ this warning, by using the [`:source` option](#SOURCE) or a
### CREDENTIALS
-Some gem sources require a username and password. Use [bundle config(1)][bundle-config(1)] to set
+Some gem sources require a username and password. Use [bundle config(1)](bundle-config.1.html) to set
the username and password for any of the sources that need it. The command must
be run once on each computer that will install the Gemfile, but this keeps the
credentials from being stored in plain text in version control.
@@ -228,7 +228,7 @@ As with groups, you can specify one or more platforms:
gem "ruby-debug", :platforms => :mri_18
gem "nokogiri", :platforms => [:mri_18, :jruby]
-All operations involving groups ([`bundle install`][bundle-install(1)], `Bundler.setup`,
+All operations involving groups ([`bundle install`](bundle-install.1.html), `Bundler.setup`,
`Bundler.require`) behave exactly the same as if any groups not
matching the current platform were explicitly excluded.