mandoc - UNIX manpage compiler toolset

	Commit message (Collapse)	Author	Age	Files	Lines
*	Rename mandoc_getarg() to roff_getarg() and pass it the roff parser	Ingo Schwarze	2018-12-21	4	-2/+58
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	struct as an argument such that after copy-in, it can call roff_expand() once again, which used to be called roff_res() before this. This fixes a subtle low-level roff(7) parsing bug reported by Fabio Scotoni <fabio at esse dot ch> in the 4.4BSD-Lite2 mdoc.samples(7) manual page, because that page used an escaped escape sequence in a macro argument. To expand escaped escape sequences in quoted mdoc(7) arguments, too, stop bypassing the call to roff_getarg() in mdoc_argv.c, function args() for this case. This does not solve the case of escaped escape sequences in quoted .Bl -column phrases yet. Because roff_expand() can make the string longer, roff_getarg() can no longer operate in-place but needs to malloc(3) the returned string. In the high-level parsers, free(3) that string after processing it.
*	Messages of the -Wbase level now print STYLE:. Since this	Ingo Schwarze	2017-07-04	7	-16/+15
\| \| \| \| \| \| \| \|	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.
*	cope with changes in BASE messages	Ingo Schwarze	2017-06-25	1	-2/+3
\|
*	style message about missing RCS ids; inspired by mdoclint	Ingo Schwarze	2017-06-17	1	-0/+1
\|
*	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/+12
\| \| \| \|	inspired by mdoclint(1), and jmc@ considers it useful
*	Macro argument quoting does not prevent recognition of punctuation	Ingo Schwarze	2017-05-30	4	-8/+9
\| \| \| \| \| \| \| \| \| \| \|	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.
*	According to the CommonMark specification, backslash escapes	Ingo Schwarze	2017-03-08	1	-1/+1
\| \| \| \|	and markdown markup do not work inside code spans.
*	first batch of -T markdown tests	Ingo Schwarze	2017-03-05	3	-0/+100
\|
*	Finally port the OpenBSD regression suite.	Ingo Schwarze	2017-02-08	6	-0/+158
\| \| \| \| \|	Both kristaps@ and wiz@ repeated asked for this, literally for years.
*	Move the regression suite to the attic.	Ingo Schwarze	2014-03-03	2	-54/+0
\| \| \| \| \| \| \|	It has not been used or maintained for several years, and we won't start using it now. Devlopment regression testing is done in OpenBSD, and there is no value in maintaining two regression suites in parallel.
*	Commit of patch floated on discuss@ a few days ago: if an in_line scope	Kristaps Dzonsons	2010-05-29	2	-0/+54
	has not been opened and closing punctuation is encountered AND the macro is marked as accepting no-content (or `Li'), then open an empty scope. Added regression tests for `Fl' and `Li' testing this behaviour. Also, squeeze hyph0.in tests into the last characters of each line so that groff doesn't hyphenate and break the test.