mandoc - UNIX manpage compiler toolset

	Commit message (Collapse)	Author	Age	Files	Lines
*	Messages of the -Wbase level now print STYLE:. Since this	Ingo Schwarze	2017-07-04	1	-5/+2
\| \| \| \| \| \| \| \|	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).
*	prevent infinite recursion while expanding the arguments	Ingo Schwarze	2017-03-08	1	-0/+1
\| \| \| \|	of a user-defined macro; issue found by tb@ with afl(1)
*	If a user-defined macro is aborted because it exceeds the stack	Ingo Schwarze	2017-03-07	1	-0/+1
	limit, usually due to infinite recursion, discard whatever remains in all those open stack levels. Otherwise, insane constructions like the following could generate macros of enormous size, causing mandoc(1) to die from memory exhaustion: .de m \" original macro definition .m \" recursion to blow up the stack .de m \" definition to be run during the call of .m marked () very long plain text (some kilobytes) .m \" expand the above a thousand times while unwinding the stack .. \" end of the original definition .m \" () recursively generate a ridiculously large macro .. \" end of recursively generated definition .m \" execute the giant macro, exhausting memory Very creative abuse found by tb@ with afl(1).