| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Fix .In formatting in the SYNOPSIS: |   Ingo Schwarze | 2017-03-07 | 2 | -1/+18 |
| | | | | | No ‌ in the middle of **, please. | ||||
| * | first batch of -T markdown tests | Ingo Schwarze | 2017-03-05 | 4 | -0/+62 |
| | | |||||
| * | Finally port the OpenBSD regression suite. | Ingo Schwarze | 2017-02-08 | 10 | -0/+129 |
| | | | | | | 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 | -22/+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. | ||||
| * | Fixed `Fd' to format in the right way. Found when confused by what the | Kristaps Dzonsons | 2010-06-04 | 1 | -0/+22 |
| hell `Fd' is supposed to do anyway (answer: it's a historical macro and we shouldn't be doing anything with it anyway). | |||||
 |
index : mandoc | |
| A git conversion mirror of mandoc.bsd.lv | User & |
| aboutsummaryrefslogtreecommitdiffstatshomepage |