| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
- Volume and arch are both optional and not alternatives.
- Zap verbiage about what's obvious from the synopsis.
- For fixed argument strings, use .Cm, not .Ar.
Using lots of input from jmc@.
Also, state that the list of valid architectures varies by OS.
If a downstream distribution wants to provide a specific list,
maintaining a local patch is the way to go.
|
|
|
|
|
| |
unescaped on a macro line, so lets just escape it;
noticed by jmc@
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Move the LANGUAGE SYNTAX from mdoc(7) and man(7) to roff(7),
it's common to both and it's actually roff syntax.
2) Move the MACRO SYNTAX down to the bottom, such that the less
technical parts MANUAL STRUCTURE and MACRO OVERVIEW get to the top.
Getting everything to again fit together after the reshuffling
required various adjustments; also adjust and improve
the DESCRIPTIONS while there.
feedback and "go ahead" jmc@ kristaps@
|
|
|
|
|
|
|
| |
each with a one-line discription. Use this when wondering
which macro fits best for your particular use case, and whether
there are alternatives.
feedback ond ok jmc@, ok kristaps@
|
| |
|
| |
|
|
|
|
| |
patch by Jason McIntyre.
|
|
|
|
| |
Directly from a patch by Jason McIntyre.
|
|
|
|
| |
out the \*q escapes. Also fix some spelling typos in both manuals.
|
| |
|
|
|
|
|
|
|
| |
note literal text in "Examples:" parts. Finally, move parts of
Quotation related to keeping whitespace into Whitespace and clean up the
text to be a bit clearer. Examples can be added back in at will, but
now it follows the general layout of explanation followed by examples.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- make examples trail each section
- make explanations more concise
- remove references to troff
ok Jason McIntyre.
|
|
|
|
|
|
| |
but avoiding use of .Nm, because letting .Nm call other macros
is unusual style, and we don't want unusual style in examples.
Issue brought up by kristaps@.
|
|
|
|
| |
ok kristaps@
|
|
|
|
|
|
| |
Originally pointed out by joerg@ then again by Thomas Klausner by way of
Nicolas Joy. Note: don't use these constructions as you can't link to
the sections with `Sx'.
|
|
|
|
|
|
| |
filling gaps found by checking the MANUAL DOMAIN chapter in mdoc.samples(7).
While here, fix lots of minor issues.
feedback and ok jmc@
|
|
|
|
|
|
|
|
|
|
| |
to "delimiters", and explain which special handling they get
as macro arguments. Move the text to a better place and remove
a few lies. Postpone figuring out the lists of macros causing
that special handling, it would cost too much time right now.
feedback and ok jmc@
This also brings the file back in sync with OpenBSD.
|
|
|
|
|
|
|
|
|
|
|
| |
explained in mdoc.samples(7) is missing from mdoc(7):
* Discourage trailing whitespace.
* Move all information about quoted arguments to the relevant
subsection, shortening it a bit, and adding an example.
* Mention that blanks can be quoted with a backslash.
* A better .Nd line in the template (verbatim from mdoc.samples(7)).
* Explain how to escape callable macro names, and provide examples.
ok jmc@
|
|
|
|
|
|
| |
* ellipsis is an argument to .Ar, not part of the preceding argument
* libz, libpam, on, off are not placeholders for arguments
* .Rv is not only relevant for system calls, see atexit(3), sem_init(3)
|
| |
|
| |
|
|
|
|
| |
using feedback from kristaps@, ok jmc@
|
| |
|
|
|
|
| |
some language for clarity.
|
|
|
|
| |
from jmc@
|
|
|
|
|
|
| |
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.
|