aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/regress/man
Commit message (Collapse)AuthorAgeFilesLines
* In no-fill mode, avoid bogus blank lines in two situations:Ingo Schwarze2019-01-052-1/+33
| | | | | 1. After the last child; the parent will take care of the line break. 2. At the .YS macro; the end of the preceding .SY already broke the line.
* In groff, when the .SY block macro occurs in no-fill mode,Ingo Schwarze2019-01-054-2/+66
| | | | the output line gets broken after the head. Do the same.
* Slowly start doing more HTML output tests, in this case for theIngo Schwarze2019-01-054-12/+44
| | | | | | | | | | | | | | | | | | | interaction of .nf and .RS, related to man_macro.c rev. 1.106. HTML regression testing is tricky because it is extremely prone to over-testing, i.e. unintentional testing for volatile formatting details which are irrelevant for deciding whether the HTML output is good or bad. Minor changes to the formatter - which is still heavily under development - might result in the necessity to repeatedly adjust many test cases. Then again, HTML syntax rules are so complicated that without regression testing, the risk is simply too high that later changes will re-introduce issues that were already fixed earlier. Let's just try to design the tests very carefully in such a way that the *.out_html files contain nothing that is likely to change, and defer testing in cases where the HTML output is not yet clean enough to allow designing tests in such a way.
* catch up with the changed order of warnings;Ingo Schwarze2018-12-312-2/+2
| | | | related to man_validate.c rev. 1.145
* Rename mandoc_getarg() to roff_getarg() and pass it the roff parserIngo Schwarze2018-12-213-13/+14
| | | | | | | | | | | | | | | | | | 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.
* Clean up the validation of .Pp, .PP, .sp, and .br. Make sure allIngo Schwarze2018-12-044-2/+12
| | | | | | | | | | | | | | combinations are handled, and are handled in a systematic manner. This resolves some erratic duplicate handling, handles a number of missing cases, and improves diagnostics in various respects. Move validation of .br and .sp to the roff validation module rather than doing that twice in the mdoc and man validation modules. Move the node relinking function to the roff library where it belongs. In validation functions, only look at the node itself, at previous nodes, and at descendants, not at following nodes or ancestors, such that only nodes are inspected which are already validated.
* In the validators, translate obsolete macro aliases (Lp, Ot, LP, P)Ingo Schwarze2018-12-031-2/+2
| | | | | | to the standard forms (Pp, Ft, PP) up front, such that later code does not need to look for the obsolete versions. This reduces the risk of incomplete handling.
* support tail arguments on the .ME and .UE macros,Ingo Schwarze2018-08-146-16/+33
| | | | used for example in the ditroff(7) manual of the groff package
* Now that we have the -Wstyle message level, downgrade six warningsIngo Schwarze2017-07-064-5/+5
| | | | | | that are not syntax mistakes and that do not cause wrong formatting or content to style suggestions. Also upgrade two warnings that may cause information loss to errors.
* Messages of the -Wbase level now print STYLE:. Since thisIngo Schwarze2017-07-04129-227/+279
| | | | | | | | 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.
* test new MT macroIngo Schwarze2017-06-258-1/+100
|
* cope with changes in BASE messagesIngo Schwarze2017-06-2532-32/+32
|
* style message about missing RCS ids; inspired by mdoclintIngo Schwarze2017-06-1734-2/+34
|
* if .in is used inside the .TP head, it's always relativeIngo Schwarze2017-06-173-1/+35
|
* improve rounding rules for scaling unitsIngo Schwarze2017-06-144-10/+10
| | | | in horizontal orientation in the terminal formatter
* Partial support for the \n[an-margin] number register.Ingo Schwarze2017-06-133-1/+42
| | | | | | | | | | | | | | | Manuals autogenerated from reStructuredText are reckless enough to peek at this non-portable, implementation-dependent, highly groff-specific internal register - for no good reason, because the man(7) language natively provides in a much simpler way what they are trying to emulate here with much fragility. A full implementation would be very hard because it would require access to output-device-specific formatting data at the roff(7) preprocessor stage, which mandoc doesn't support at all. So hardcode a few magic numbers as reStructuredText expects them for terminal output. For other output modes (like HTML), code using this register is utterly broken anyway.
* ignore blank lines in man(7) next line scope;Ingo Schwarze2017-06-0316-2/+55
| | | | strange groff edge case behaviour found in multimedia/mjpegtools
* Move .sp to the roff modules. Enough infrastructure is in placeIngo Schwarze2017-05-051-0/+4
| | | | now that this actually saves code: -70 LOC.
* Now that markdown output is tested for almost everything, test allIngo Schwarze2017-03-081-0/+1
| | | | | | 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.
* more tests for .IP/.nf interaction that i forgot to commitIngo Schwarze2017-02-172-2/+69
|
* Finally port the OpenBSD regression suite.Ingo Schwarze2017-02-08218-0/+4254
| | | | | Both kristaps@ and wiz@ repeated asked for this, literally for years.
* Move the regression suite to the attic.Ingo Schwarze2014-03-0317-127/+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.
* Forgot to add regression tests.Kristaps Dzonsons2010-05-251-0/+15
|
* Test .SH with only empty paragraph. Don't test .IP without body.Joerg Sonnenberger2010-05-221-0/+3
|
* Multiple empty .PPs don't add a vspace eitherJoerg Sonnenberger2010-05-171-0/+3
|
* Add support for .AT. Properly implement .UC. Add regress tests.Joerg Sonnenberger2010-05-1713-0/+67
|
* Tests for sane and insane handling of lines before and after .SH/.SSJoerg Sonnenberger2010-05-172-0/+23
|
* Add a test case for nesting of .RS/.REJoerg Sonnenberger2010-05-161-0/+16