| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
for the case of multiple sibling macros on a single input line.
Issue found investigating a question from sobrado@.
"I like this diff" kristaps@
|
|
|
|
|
|
|
|
|
|
| |
non-macro lines as "text lines" (after defining them as such). Clean up
notion of font scope. Note comma usage in multiple `Nm's. Note
ordering of SYNOPSIS section stuff. Add some bits about DESCRIPTION
syntax (brief description, then args). Note that `Bl' can also contain
HEAD. Finally, fix some `Cm' entries to be properly `Ar'.
Ok Jason McIntyre.
|
|
|
|
|
| |
included in the brackets. We really should have a warning about this,
but that'll wait for another day.
|
|
|
|
| |
'...' have a properly-escaped initial dot.
|
|
|
|
| |
characters. Use "Reserved Terms" instead.
|
|
|
|
|
|
|
|
|
|
|
|
| |
as a first step to get rid of the frequent petty warnings in this area:
- always store dates as strings, not as seconds since the Epoch
- for input, try the three most common formats everywhere
- for unrecognized format, just pass the date though verbatim
- when there is no date at all, still use the current date
Originally triggered by a one-line patch from Tim van der Molen,
<tbvdm at xs4all dot nl>, which is included here.
Feedback and OK on manual parts from jmc@.
"please check this in" kristaps@
|
|
|
|
| |
of how we considered .TS (etc.) macros and how the preprocessors do.
|
|
|
|
| |
ok kristaps@ jmc@.
|
|
|
|
|
| |
shitty groff behaviour. Do the same, but raise a warning to this
effect. This from a TODO noted by schwarze@.
|
|
|
|
|
|
| |
on a UNIX system use UNIX conventions, and UNIX tools working
on them expect that.
ok jmc@
|
|
|
|
| |
Check prompted by kristaps@.
|
|
|
|
| |
shall precede outputted text (surprise!).
|
|
|
|
| |
Added cross-links to tbl.7 from other manuals.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
1. improve .Bl wording (from jmc@)
2. jmc@ noted that the .Mt default (the same as in groff) makes no sense,
and there is no better default we could use; thus, regard it as
implementation dependent and do not document it
3. fix formatting of one COMPATIBILITY note: move "and" out of .Sx
ok kristaps@, jmc@
|
|
|
|
|
|
|
|
| |
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.
|
| |
|