summaryrefslogtreecommitdiffstats
path: root/regress/roff/de/Makefile
Commit message (Collapse)AuthorAgeFilesLines
* trivial sync with OpenBSDIngo Schwarze2020-07-301-6/+6
| | | | | in parts of these files that are not used by -portable; consequently, no functional change
* When calling an empty macro, do not clobber existing arguments.Ingo Schwarze2019-04-211-3/+3
| | | | | Fixing a bug found with the groffer(1) version 1.19 manual page following a report from Jan Stary.
* Let roff_getname() end the roff identifier at a tab characterIngo Schwarze2019-02-061-3/+4
| | | | | | | | | | | | | | | | | | | | | | and audit all its callers whether termination is handled correctly. Resulting improvements: * An escape or tab ending the macro name in a macro invocation is discarded, and argument processing is started after it. * An escape or tab ending a name in ".if d" and ".if r" is preserved. * An escape ending a name in ".ds" causes the whole request to be ignored. * A tab ending a name in ".ds" becomes part of the string. * An escape or tab ending a name in ".rm" causes the rest of the line to be ignored. * An escape or tab ending the first name in ".als", ".rn", or ".nr" causes the whole request to be ignored. Kurt Jaeger <pi at FreeBSD> made me aware of https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235456#c0 and in that bug report, comment 0 item (3) is a special case of this class of issues. Yes, the "mh" manual pages are no doubt among the worst on the planet.
* Messages of the -Wbase level now print STYLE:. Since thisIngo Schwarze2017-07-041-2/+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.
* If a user-defined macro is aborted because it exceeds the stackIngo Schwarze2017-03-071-2/+7
| | | | | | | | | | | | | | | | | | | 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).
* Finally port the OpenBSD regression suite.Ingo Schwarze2017-02-081-0/+44
Both kristaps@ and wiz@ repeated asked for this, literally for years.