| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
desired output files could be run with an arbitrary roff(7) implementation;
in reality, it only makes sense to run them with groff(1).
Also, there is really no point in allowing the groff command line arguments
to be overridden; running these targets only makes sense with exactly the
right options. So get rid of the fragile ?= and += construct for groff
options and make sure the options are always passed in a reasonable order.
Finally, use groff(1) directly rather than the shallow nroff(1) wrapper
because GNU nroff(1) does not support running the GNU eqn(1) preprocessor,
which will probably be needed soon, and also because it simplifies using
the GNU tbl(1) preprocessor.
|
| |
|
|
|
|
|
|
| |
causes horrible churn anyway, profit of the opportunity to stop
excessive testing, such that this is hopefully the last instance
of such churn. Consistently use OpenBSD RCS tags, blank .Os,
blank fourth .TH argument, and Mdocdate like everywhere else.
Use -Ios=OpenBSD for platform-independent predictable output.
|
| | |
|
| | |
|
| |
|
|
| |
triggered by a bug report from jsg@
|
| | |
|
| | |
|
|
|
Groff forces the document author to manually request sufficient spacing
after .TE - that is, at least .sp 1v after a table with the "box" option
and at least .sp 2v after a table with the "doublebox" option - or else
it clobbers the box. I consider that insane, so i'm not imitating groff
in that respect. Instead, i add at least as much vertical space as groff,
or more where required to avoid clobbering the box.
Consequently, output will be identical for input that looks sane with
groff, and mandoc will make output look better for input that looks bad
with groff.
As a side effect, having identical output for portable input
makes it possible to set up the first regression tests for tbl(7).
|
schwarze