| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
|
| |
separated by only "and" while two or more are with ", and" for the last
author.
Also remove relevant TODO and add regression tests.
|
| |
|
|
|
|
| |
fully accomodates for the pod2man standard preamble!
|
|
|
|
| |
Jason. Patch by Jason.
|
|
|
|
| |
assigned within the pod2man preamble.
|
|
|
|
|
|
| |
experimental and hasn't been rigorously tested. It's only implemented in
-mdoc for the time being. This is absolutely required for pod2man. It
does, however, make the pod2man preamble be processed in full.
|
|
|
|
|
| |
should be printing the contents, but for the time being, this is good
enough.
|
| |
|
|
|
|
| |
OpenBSD compatibility notes. Based on a patch by Jason McIntyre.
|
|
|
|
|
|
| |
sys/types.h is the file you want to include."
From a downstream fix by deraadt@.
|
| |
|
|
|
|
|
| |
definitely not general, but it's good enough for pod2man definitions
(after I clean up the roff, which will be addressed in later fixes).
|
| |
|
| |
|
|
|
|
| |
care because pod2man uses this construct.
|
|
|
|
| |
getting mandoc ready to handle pod2man's complex escapes.
|
|
|
|
| |
detective-work in the UNIX archives.
|
|
|
|
| |
Update escape COMPATIBILITY in mdoc(7) and man(7) (ok schwarze@).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As Kristaps found out, i was wrong: .Bl -column phrases do not ignore
spacing rules for trailing punctuation in general. In particular,
- the rightmost column of a column list is unaffected
- columns terminated by the .Ta macro instead of a tab are unaffected
- columns ending in a blank are unaffected
Spacing rules for trailing punctuation are only ignored when the tab
follows the punctuation immediately, without a blank in between,
because then the combination of punctuation and tab is treated by roff
as a word, and the punctuation is not recognized as isolated.
The reason this doesn't work in mandoc is that in the special case
of .Bl -column (not in general!), mandoc treats tabs as word delimiters.
We either need to solve this differently, or call it a bug in roff.
|
|
|
|
|
| |
making the code simpler and easier to understand.
No functional change.
|
|
|
|
|
| |
to the start of the next column correctly.
Fixing a problem found by jmc@ in sysctl(3), reminded by kettenis@.
|
|
|
|
|
| |
and render it just like normal text.
Minimal fix of a formatting bug in operator(7) reported by ray@.
|
|
|
|
|
| |
skip output functions, but not *_endparse;
problem reported by kristaps@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We now have sufficient practical experience to know what we want,
so this is intended to be final:
- provide -Wlevel (warning, error or fatal) to select what you care about
- provide -Wstop to stop after parsing a file with warnings you care about
- provide consistent exit status codes for those warnings you care about
- fully document what warnings, errors and fatal errors mean
- remove all other cruft from the user interface, less is more:
- remove all -f knobs along with the whole -f option
- remove the old -Werror because calling warnings "fatal" is silly
- always finish parsing each file, unless fatal errors prevent that
This commit also includes a couple of related simplifications behind
the scenes regarding error handling.
Feedback and OK kristaps@; Joerg Sonnenberger (NetBSD) and
Sascha Wildner (DragonFly BSD) agree with the general direction.
|
| |
|
| |
|
|
|
|
| |
installed on the host system.
|
|
|
|
| |
flat-out ignore them.
|
| |
|
|
|
|
|
|
| |
when being used in manuals. Since we now support `ds', it's no longer
necessary to account for it. From a bug report originally by Thomas
Jeunet.
|
|
|
|
|
|
| |
Also made sign-less \s-style escapes be ok (this is technically against
what's in the groff.7 manual, but seems pretty widespread). Noted by
Thomas Jeunet as uglifying the gcc.1 manual.
|
| |
|
| |
|
|
|
|
| |
Note also that the PDF file should be reduced in case I somehow forget.
|
|
|
|
| |
Berzoja. Also note COMPATIBILITY of groff misformatting `Lk'.
|
|
|
|
| |
Behaviour ok'd by schwarze@.
|
|
|
|
|
| |
accompagnying comment between man_pmacro() and mdoc_pmacro();
ok'd by kristaps@ together with main.c rev. 1.102
|
|
|
|
|
|
| |
For example, on OpenBSD without locale settings,
isgraph(3) returns true for some eight-bit characters.
ok kristaps@
|
|
|
|
|
| |
were never taken since main.c begin skipping over unrecognisable
characters, so they were noops.
|
|
|
|
|
| |
by a tab; so allow the tab in mandoc, too." Original problem noted by
schwarze@. Sync with OpenBSD.
|
| |
|
| |
|
|
|
|
|
| |
preserve blank lines at the end of .Bd -literal
patch from kristaps@, who asked me to commit this
|
|
|
|
|
|
| |
preserve blank lines in .Bd -literal,
both in the middle and at the end of the display
ok kristaps@
|
|
|
|
| |
troff. This removes the last groff(1) `Xr'.
|
|
|
|
| |
Put "remarks" for `%C' into COMPATIBILITY.
|
| |
|