| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
manual output in existing HTML or XHTML documents, e.g., when invoking
mandoc from an SSI or CGI.
|
| |
|
|
|
|
|
| |
fixes lynx's rendering of manuals with the \&, which were rendering as
​ in the text. Reported by Paul de Weerd, thanks!
|
|
|
|
|
|
|
|
| |
implement .Bl -bullet
add more information to the .TH line
escape dots at the beginnings of lines
add trailing newline character at the end of the file
do not misinterpret the ROOT block as .Ap
|
| |
|
|
|
|
|
| |
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@
|
|
|
|
|
| |
specifier that makes it look nicer;
from jmc@, ok kristaps@
|
| |
|
|
|
|
|
|
|
| |
forget about pending whitespace (vbl), or the next line would
be misaligned and potentially too long; but i'm fixing this
in a simpler way than he proposed.
Also remove the kludges in .HP that compensated for this bug.
|
|
|
|
| |
after Werner Lemberg committed a patch by Joseph Koshy
|
|
|
|
|
| |
to work both with and without frames and rulers.
ok kristaps@
|
|
|
|
| |
writing this for man(7), too, was suggested by kristaps@
|
|
|
|
|
|
|
| |
to have *next*-line head arguments on the *same* input line.
So .TP must not assume that a head argument with a matching
input line number is a same-line argument (and access a NULL pointer).
Bug found and fix tested by kristaps@ with groff_hdtbl(7).
|
|
|
|
|
| |
to variables that might be changed;
from kristaps@
|
|
|
|
|
|
| |
to the default and check that the left does not outgrow the right one.
Otherwise, the (rmargin >= offset) assertion fails in term_flushln().
Bug found and fix tested by kristaps@ with NetBSD slapo-retcode(5).
|
|
|
|
|
|
| |
this was forgotten after man_term.c rev. 1.25 on March 2, 2010.
The benefit is a sane page header line when .Dt is very long.
Reminded by Thomas Klausner <wiz at NetBSD>, thanks.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In columnated contexts (.Bl -column, .Bl -tag, .IP, .TP, .HP etc.), do not
pad after writing a column. Instead, always pad before writing content.
In itself, this change avoids:
- writing trailing whitespace in some situations
- with .fi/.nf in .HP, breaking lines that were already padded
It allows several bugfixes included in this patch:
- Do not count backspace as a character with positive width.
- Set up proper indentation when encountering .fi/.nf in .HP.
- Adjust the .HP indentation width to what groff does.
- Never unlimit the right margin unless in the final column.
ok kristaps@
|
|
|
|
|
| |
is both preceded and followed by an alphabetic character.
ok kristaps@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a string is defined in terms of itself, the REPARSE_LIMIT in read.c
used to break the cycle. This no longer works since all the work
is now done in the function roff_res(), looping indefinitely.
Make this loop finite by arbitrarily limiting the number of times one
string may be expanded; when that limit is reached, leave the remaining
string references unexpanded.
This changes behaviour compared to 1.11.5, where the whole line would
have been dropped. The new behaviour is better because it loses less
information. We don't want to imitate groff-1.20.1 behaviour anyway
because groff aborts parsing of the whole file.
ok kristaps@
|
|
|
|
|
| |
even a breakable hyphen may be bold or underlined
ok kristaps@
|
|
|
|
|
|
|
|
| |
This patch was originally written in July 2011 by kristaps@,
i promptly committed it to OpenBSD, and then it was forgotten.
Now i rediscovered it when merging 1.11.7 to OpenBSD.
ok kristaps@ (on his own patch :)
|
| |
|
|
|
|
| |
found while syncing to OpenBSD
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
|
|
| |
to convert mdoc(7) documents to the man(7) language.
This is work in progress and will be developed in tree.
It does already handle the cat(1) manual,
but will hardly handle all your fancy manuals yet.
go ahead kristaps@ jmc@ millert@ deraadt@
|
|
|
|
| |
found while merging to OpenBSD
|
| |
|
|
|
|
| |
portable, so document it in COMPATIBILITY.
|
| |
|
| |
|
|
|
|
|
| |
backend (the front-end already accomodated for this). Found indirectly
from a question by Brad Smith.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
well as leading punctuation. Again, this isn't the same as deroff
(which uses, I think, some punctuation as delimiters), but it's easier
to explain and simpler to audit.
|
|
|
|
|
|
| |
any other deroff manual, and as I don't think anybody actually uses
deroff, I don't feel compelled to research its behaviour too much and
can just do what's logical.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
patch by Jason McIntyre.
|
|
|
|
| |
Directly from a patch by Jason McIntyre.
|
|
|
|
| |
doing manpages.bsd.lv stuff.
|
|
|
|
| |
Klausner.
|
|
|
|
| |
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.
|