| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
about deprecation, because there are cases were choosing .Xo or
backslash line continuation is merely a matter of taste, not a
difference in readability, and well-used .Xo is even slightly
more portable.
OK jmc@
|
|
|
|
|
|
|
|
|
|
| |
for the new libroff macros, the new libman macros, and for the sake of
general clarity.
Note that `ft' documentation is NOT included, as I've kept it in -man:
it's highly confusing to have it in roff.7 when it's not implemented for
both -man and -mdoc, as at least in theory, roff.7 should include only
macros recognised by BOTH formats.
|
|
|
|
|
|
|
| |
making sure output doesn't add a superfluous newline with the nested displays.
Also add a COMPATIBILITY note.
Rename a macro (DATESIZ) to be in line with OpenBSD (DATESIZE).
|
|
|
|
| |
as pointed out by kristaps@. Sorry!
|
|
|
|
|
|
|
|
| |
Define the terms "callable" and "parsed" with more precision.
Be more specific about what .Xo can be used for.
Be more specific about what "historic groff" refers to.
Explicitely mention the nine argument limit below COMPATIBILITY.
feedback and ok jmc@
|
|
|
|
| |
Document that `Pa' is replaced by a tilde, just like `Mt'.
|
|
|
|
|
|
|
|
| |
Clarify that `Mt' gets a default `~' (as per groff 1.20) and document it
in mdoc.7.
Made `Lk' be removed in mdoc_macro.c if it has no arguments. This fixes
segfaults in mdoc_{term,html}.c that nobody's managed to raise yet.
|
|
|
|
|
|
| |
Otherwise, hyperlinks can't be produced and people will likely
miss the additional information available.
Suggested by deraadt@.
|
|
|
|
| |
Prodded by guenther@, ok jmc@.
|
|
|
|
| |
macros within an unfilled or literal `Bd'.
|
| |
|
|
|
|
|
|
| |
note that IMPLEMENTATION NOTES is not used in OpenBSD
add missing comma in "sections 1, 6, & 8 only" below EXIT STATUS
below SEE ALSO, add an .Xr to man(1), and from man(7) to mdoc(7)
|
|
|
|
| |
Jason. Patch by Jason.
|
|
|
|
|
| |
should be printing the contents, but for the time being, this is good
enough.
|
|
|
|
| |
OpenBSD compatibility notes. Based on a patch by Jason McIntyre.
|
| |
|
| |
|
| |
|
|
|
|
| |
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@).
|
|
|
|
| |
Berzoja. Also note COMPATIBILITY of groff misformatting `Lk'.
|
|
|
|
| |
troff. This removes the last groff(1) `Xr'.
|
|
|
|
| |
Put "remarks" for `%C' into COMPATIBILITY.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* correct a few obvious mistakes
* adopt some of jmc@'s recent changes to man(7)
* cut down just a little on the awful tendency
to stick a hyphen between two words.
|
|
|
|
|
|
| |
- HISTORY is interesting even when there are STANDARDS
- more precise instructions what to put into AUTHORS
- add the version argument to the mdoc(7) .Os macro
|
|
|
|
| |
started by Sascha Wildner, 07/25/2010 06:30 AM.
|
|
|
|
|
|
| |
nit noted by Jason McIntyre.
"your diff looks ok" (Jason McIntyre)
|
| |
|
|
|
|
|
| |
Noted in arch.in and st.in that mdoc.7 must be updated if entries are
added.
|
|
|
|
|
|
|
|
|
| |
Applied "new-sentence, new-line" here and there.
Refer to "whitespace", not "white-space".
Remove long-commented-out CAVEATS, all of which have been addressed or
at least discussed to some extent or another.
|
| |
|
|
|
|
|
|
| |
will.
Also whack the dot-separator from the embedded man.7 manual.
|
| |
|
| |
|
| |
|
|
|
|
| |
`Pa', `Pc', `Po', `Pq', `Pp', and `Va'.
|
|
|
|
| |
Document `Eo' and `Ec'. Add context-end notes `Ec' and `Fc'.
|
|
|
|
|
| |
on those parts of the code and text that i have written as Kristaps is.
"fine with me" kristaps@
|
| |
|
|
|
|
|
|
|
| |
kristaps@ will do the missing HTML part soon.
"looks nicer" jmc@
"seems perfect to me" sobrado@
"slap it in" kristaps@
|
| |
|
|
|
|
|
|
|
| |
sure where this came about. Added regression tests to convince myself
that this is so. Also consolidated COMPATIBILITY notes regarding `Bd'.
Added COMPATIBILITY note to the effect that old groff pukes on `Bd
-compact -ragged' (regression test will fail on old groff).
|
|
|
|
|
|
|
|
|
|
|
| |
only calculated once in mdoc_validate.c.
Noted that `Bd -file xxx' is not supported: it now raises a fatal
warning. This is noted in mdoc.7.
Empty `Bd' now defaults to LIST_ragged, which is not quite what groff
does, but close enough (gross just throws away the `Bd' and gets upset
when it encounters an `Ed').
|
|
|
|
| |
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.
|
| |
|