| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
within term.c, but does add a small shim over putchar() that switches on
the output engine. Prints, for this initial version, only monospace and
without font decorations. It's a start.
|
|
|
|
| |
Spell-checked manuals.
|
|
|
|
| |
EOLN whitespace fixed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
thousand years ago. Note that this is normalised to >=60.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Restore the blank line before .In in SYNOPSIS
except right after .Sh or right after another .In.
Even though Kristaps says SYNOPSIS blank-line handling
is still very much work in progress and more is probably needed,
this one is useful to keep in sync with OpenBSD.
"fine" kristaps@
|
|
|
|
| |
otherwise.
|
| |
|
| |
|
|
|
|
|
|
| |
Better documentation for `Fa' and some others.
Added `Ft', `Fo', and some COMPATIBILITY notes.
|
|
|
|
| |
`Fn'.
|
|
|
|
|
|
|
| |
extent.
Documented `Fn'. Please note the COMPATIBILITY note regarding historic
groff.
|
|
|
|
|
|
| |
Fixed `In' to behave properly: it wasn't properly breaking lines,
formatting, or really anything else. Noted COMPATIBILITY with
OpenBSD's groff, which pukes all over `In'.
|
|
|
|
|
| |
hell `Fd' is supposed to do anyway (answer: it's a historical macro and
we shouldn't be doing anything with it anyway).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
the peculiarities with `It'-less `Bl -column' invocations, column
phrases, per-type syntax of `It', etc.
|
|
|
|
|
|
|
|
|
|
| |
relieves having to repeat running over the argument list in
mdoc_action.c and mdoc_validate.c.
Default to LIST_item for type-less lists (groff technically doesn't do
this: it just ignores the `It' lines altogether).
Make MANDOC_LISTTYPE be a recoverable error.
|
|
|
|
| |
(as per Jason McIntyre's suggestion for manuals in general).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Fixed flushed-out condition of \} causing subsequent arguments to be
truncated, when in fact the whole line should be passed through (if the
conditional succeeds) to the front-end and the \} ignored there.
Added regression test of this behaviour.
|
| |
|
|
|
|
|
|
|
|
| |
list).
Reverted MANDOC_COLUMNS to be a bad-bad syntax error: we don't, and
apparently never have, allowed mixing of -column syntaxes. This would
have segfaulted if encountered.
|
|
|
|
|
| |
instead of iterating over arguments and only scan with `-column', which
needs the count of arguments.
|
| |
|
|
|
|
|
| |
hyphen wasn't resetting the fact of being whitespace. Noted by Jason
McIntyre.
|
|
|
|
|
|
|
| |
or a closed-out `It' block within a `Bl -column' (which only happens
when a macro or free-form text is encountered prior to an `It').
Added some regression tests for this behaviour.
|
|
|
|
| |
Added regression test for constrained condition.
|
|
|
|
|
|
|
|
| |
-column' up until the first `It'. This is UGLY and should have all
sorts of warnings, and will. On the one hand, it fits with groff's
notion of tabs and tab-spaces. On the other hand, it's not really
"free-form" text any more. Note that this does not yet accomodate for
macros coming on these lines.
|
|
|
|
| |
processing.
|
|
|
|
| |
comes into play).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add `Ta' macro, which is basically a NULL case everywhere but in
mdoc_macro.c, where it closes out an existing `It' body scope and opens
a new one, then continues parsing as in phrase() (TODO: merge these
two?).
Fix where scope-breaking was silently just dying instead of printing an
error.
Fix where trailing `Ta' or tab weren't creating a new MDOC_BODY context.
We now support arbitrarily complex `It' contents for `Bl -column'.
|
| |
|
| |
|
|
|
|
|
| |
open scopes to migrate across tabs) that we probably won't support and
is well-known.
|
|
|
|
|
|
|
|
|
|
| |
will make it easy for re-entrant parsing of `Ta' macros to fit in with
standard closure rules.
Added some more regressions for `Bl -column'. Note that one should
fail, as documented in the TODO file.
Recorded change of AST BNF in mdoc.3.
|
|
|
|
|
| |
be changing this around and want a record in CVS of what was happening
beforehand.
|
|
|
|
| |
handling.
|
|
|
|
|
|
|
|
| |
supported (which works but is tricky enough that it should be broken
down into digestable parts). This simply moves around the propogation
of ARGS_PEND into one recognised by phrase().
Added a few regressions for simple -column lists.
|
| |
|