mandoc - UNIX manpage compiler toolset

	Commit message (Collapse)	Author	Age	Files	Lines
*	Style message about legacy man(7) date format in mdoc(7) documents	Ingo Schwarze	2017-06-11	1	-0/+1
\| \| \| \| \|	and operating system dependent messages about missing or unexpected Mdocdate; inspired by mdoclint(1).
*	style message about missing blank before trailing delimiter;	Ingo Schwarze	2017-06-10	4	-3/+4
\| \| \| \|	inspired by mdoclint(1), and jmc@ considers it useful
*	Macro argument quoting does not prevent recognition of punctuation	Ingo Schwarze	2017-05-30	3	-3/+3
\| \| \| \| \| \| \| \| \| \| \|	and of called macros. This bug affects almost all macros, and fixing it simplifies the code. It is amazing that the bogus ARGS_QWORD feature got implemented in the first place, and then carrier along for more than eight years without anybody ever noticing that it was pointless. Reported by Leah Neukirchen <leah at vuxu dot org>, found on Void Linux.
*	Now that markdown output is tested for almost everything, test all	Ingo Schwarze	2017-03-08	1	-1/+0
\| \| \| \| \| \|	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.
*	Fix .In formatting in the SYNOPSIS:	Ingo Schwarze	2017-03-07	3	-1/+61
\| \| \| \|	No &zwnj; in the middle of **, please.
*	first batch of -T markdown tests	Ingo Schwarze	2017-03-05	3	-0/+27
\|
*	Finally port the OpenBSD regression suite.	Ingo Schwarze	2017-02-08	10	-0/+136
\| \| \| \| \|	Both kristaps@ and wiz@ repeated asked for this, literally for years.
*	Normalise SYNOPSIS behaviour after I gave up on following groff's	Kristaps Dzonsons	2010-06-07	1	-24/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	inconsistent behaviour. In short: Some macros are displayed differently in the SYNOPSIS section, particularly Nm, Cd, Fd, Fn, Fo, In, Vt, and Ft. All of these macros are output on their own line. If two such dissimilar macros are pair-wise invoked (except for Ft before Fo or Fn), they are separated by a vertical space, unless in the case of Fo, Fn, and Ft, which are always separated by vertical space. Behaviour ok Jason McIntyre, ingo@. Fallout will be treated case-by-case. I had to clear out some regressions that were testing against groff's stranger behaviours: these will now break, as we don't care about such invocations. Also removed the newline for `Cd' invocation in a non-SYNOPSIS context.
*	Documented `In' in full.	Kristaps Dzonsons	2010-06-04	1	-0/+24
	Fixed `In' to behave properly: it wasn't properly breaking lines, formatting, or really anything else. Noted COMPATIBILITY with OpenBSD's groff, which pukes all over `In'.