man/man1/binman.1 in binman-0.1.1 vs man/man1/binman.1 in binman-0.1.2
- old
+ new
@@ -1,6 +1,6 @@
-.TH BINMAN 1 "2011-10-13" "0.1.1" "Ruby User Manuals"
+.TH BINMAN 1 "2011-10-13" "0.1.2" "Ruby User Manuals"
.SH NAME
.PP
binman \- UNIX man pages for Ruby \fBbin/\fP scripts
.SH SYNOPSIS
.PP
@@ -13,17 +13,31 @@
into
.BR roff (7)
using \fBRedcarpet2\fP \fIhttps://github.com/tanoku/redcarpet\fP, and display them using
.BR man (1).
.SS Leading Comment Headers
+.PP
+A leading comment header can be one of the following two things:
.nr step 0 1
.IP \n+[step]
A contiguous sequence of single-line comments starting at the
beginning of the file (after shebang and encoding comments plus
optional blank lines) and ending at the first single blank line.
.IP \n+[step]
First embedded document delimited by \fB=begin\fP and \fB=end\fP lines.
.SS Markdown Processing Extensions
+.PP
+The following \fBRedcarpet2\fP \fIhttps://github.com/tanoku/redcarpet\fP markdown processing extensions are enabled:
+.
+.IP \[bu] 2
+autolink
+.IP \[bu] 2
+no_intra_emphasis
+.IP \[bu] 2
+fenced_code_blocks
+.IP \[bu] 2
+space_after_headers
+.SS Markdown Processing Divergence
.PP
Although your leading comment headers are written in
.BR markdown (7),
\fBbinman\fP
introduces the following additional conventions to simplify common tasks: