Align to the new, sane behaviour of the groff_mdoc(7) .Dd macro:
without an argument, use the empty string, and always concatenate
all arguments, no matter their number.
This allows reducing the numb

Align to the new, sane behaviour of the groff_mdoc(7) .Dd macro:
without an argument, use the empty string, and always concatenate
all arguments, no matter their number.
This allows reducing the number of arguments of mandoc_normdate()
and some other simplifications, at the same time polishing some
error messages by adding the name of the macro in question.

show more ...

Give up on the illusion that the maintainer targets for regenerating the
desired output files could be run with an arbitrary roff(7) implementation;
in reality, it only makes sense to run them with g

Give up on the illusion that the maintainer targets for regenerating the
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.

show more ...

Now that markdown output is tested for almost everything, test all
input files in -T markdown output mode by default and only mark
those files with SKIP_MARKDOWN that are not to be tested.
Much easie

Now that markdown output is tested for almost everything, test all
input files in -T markdown output mode by default and only mark
those files with SKIP_MARKDOWN that are not to be tested.
Much easier to read, and almost minus 40 lines of Makefile code.

show more ...

first batch of -T markdown tests

We repeatedly observed assertion crashes in the low-level terminal
output handler because the high level terminal formatters could be
tricked into setting the left margin further to the right than th

We repeatedly observed assertion crashes in the low-level terminal
output handler because the high level terminal formatters could be
tricked into setting the left margin further to the right than the
right margin. Today, jsg@ found more of these with afl.

Change the internal interface between both levels, aiming for
simplicity and robustness of the code. Treat both margins as
*independent* settings: Now, termp.offset is the requested left
margin, and termp.rmargin is the available space. Let the lower
level cope with that case of insufficient space.

Obviously, high level code that does centering or flush right
still has to do careful checks, so i did a full audit of margin
settings in the terminal formatters.

Fixes crashes caused by excessively long title or date strings in
the man(7) footer, operating system or date strings in the mdoc(7)
footer, volume strings in the man(7) or mdoc(7) header, and a few
cases related to some non-prologue macros.

show more ...

new regression tests collected during recent work