| Age | Commit message (Collapse) | Author |
|---|
|
* .nr optional third argument (auto-increment step size)
* \n+ and \n- numerical register auto-increment and -decrement
bentley@ reported on Dec 9, 2013 that lang/sbcl(1) uses these.
|
|
the previous commit for strings and macros, only technically simpler.
Desired behaviour also mentioned by Werner Lemberg in 2011.
This diff adds functionality but is -21 +19 LOC. :-)
|
|
Observed by Werner Lemberg on Nov 14, 2011
and rotting on my TODO list ever since.
|
|
some of them with an optional variable name following:
- .Ft
- .Fa in the SYNOPSIS
- .Fn second and later arguments in the SYNOPSIS
So add these to the .Vt macro table in the mandoc.db(5) database.
During my LibreSSL work, i'm getting really tired of typing
$ man -k Vt,Ft,Fa=some_type_name
over and over again; now, this becomes just:
$ man -k Vt=some_type_name
|
|
|
|
partial explicit macros. Leah Neukirchen <leah at vuxu dot org>
rightfully points out that the check makes no sense for these macros.
|
|
in both groff and mandoc
|
|
|
|
One benefit is a reduced probablity that a blank appears between
a function name and the opening parenthesis introducing the arguments.
The heuristics isn't perfect and may occasionally suppress a blank
that wouldn't do harm.
|
|
that can be changed unilaterally because groff fails to render them
at all.
|
|
entry, print a meaningful warning and skip the entry.
The tests now require the actual manual pages to be around in
addition to the database, they find more results and print more
warnings.
|
|
|
|
Adapt test.
OK schwarze@
|
|
|
|
and it is causing too much trouble in -portable.
|
|
on other operating systems where mandoc is not installed,
causing the test to fail in the portable test suite.
|
|
|
|
|
|
Print the right character for mathematical overbar.
|
|
committed by bentley@ in html.c rev. 1.86
|
|
|
|
|
|
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.
|
|
|
|
L. Cherry, "Typesetting Mathematics - User's Guide (Second Edition)",
August 15, 1978, paragraph 23; swarm of bugs pointed out by bentley@.
|
|
Cures bogus error messages in pages generated with pod2man(1).
|
|
i thought. Fixing a bug in curs_addch(3) and minus 25 lines of code.
|
|
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.
|
|
triggered by a question from Yuri Pankov (illumos)
|
|
|
|
by an isolated closing delimiter; inspired by mdoclint
|
|
|
|
|
|
|
|
|
|
|
|
With roff_getstrn(), provide finer control which definitions
can be used for what:
* All definitions can be used for .if d tests and .am appending.
* User-defined for \* expansion, .dei expansion, and macro calling.
* Predefined for \* expansion.
* Standard macros, original or renamed, for macro calling.
Several related improvements while here:
* Do not return string table entries that have explicitly been removed.
* Do not create a rentab entry when trying to rename a non-existent macro.
* Clear an existing rentab entry when the external interface
roff_setstr() is called with its name.
* Avoid trailing blanks in macro lines generated from renamed
and from aliased macros.
* Delete the duplicate __m*_reserved[] tables, just use roff_name[].
|
|
|
|
|
|
|
|
|
|
* Do not discard data that lacks a matching layout cell but remains
within the number of columns of the table as a whole.
* Do not insert dummy data rows for any layout row starting with a
horizontal line, but only for layout rows that would discard all
the data on a matching non-empty data row.
* Print horizontal lines specified in the layout even if there is
no matching data cell.
* Improve the logic for extending vertical lines to adjacent rows,
for choosing cross marks versus line segments, and some related details.
|
|
|
|
used for example by zoem(1)
|
|
This clearly works when .po is called on the top level, but might
not be sophisticated enough if people call .po inside indentation-changing
contexts, but i haven't seen that in manual pages (yet :).
|
|
abused by mail/nmh; groff_char(7) confirms that this really exists
|
|
|
|
in horizontal orientation in the terminal formatter
|
|
|
|
|
