| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
so that everybody can use them. This follows the convention of
libXXXX.h being internal to a library and XXXX.h being the external
interface. Not only does this allow the removal of lots of redundant
NULL-checking code, it also sets the tone for adding new mandoc-global
routines.
|
|
|
|
| |
which is wrong. Then remove mdoc_iscdelim() alltogether.
|
|
|
|
|
|
| |
later be modified to remove the need for iscdelim(), which will be used
to unify delimiter checks, which will then allow for the simple removal
of a TODO regarding escaped periods.
|
|
|
|
| |
from Christian Weisgerber <naddy at openbsd dot org>
|
|
|
|
|
|
| |
over an array of possible argument types, hooking in to mdoc_argnames[].
This knocks off bytes for the duplicated strings and cleans up code
readability.
|
| |
|
| |
|
| |
|
|
|
|
| |
the direction of this particular patch", schwarze@.
|
| |
|
|
|
|
|
| |
found by Ulrich Spoerlein <uqs at freebsd> using the clang static analyzer;
"ok, but please document the numbers" kristaps@
|
|
|
|
|
|
|
|
|
| |
into PostScript and PDF documents behind the user's back.
Joerg Sonnenberger pointed out that almost all software
creating PostScript and PDF documents does so, even on OpenBSD,
but that doesn't make the leakage much better in my book.
According to all standards i could find, this information is optional.
Issue originally reported by deraadt@; "commit!" kristaps@.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
| |
|
|
|
|
| |
with missing function prototypes. Ok joerg@.
|
|
|
|
|
|
|
|
|
| |
heavily based on a patch from kristaps@ with some tweaks by me.
- Also talk about -Tps and -Tpdf.
- Use the same list style as in the other mandoc manuals.
- Replace a few macros by ones better suited.
- Some improvements of wording.
ok jmc@ kristaps@
|
|
|
|
| |
of how we considered .TS (etc.) macros and how the preprocessors do.
|
|
|
|
| |
the concatenated string (in -T[x]html, it gets a SPAN, too).
|
| |
|
|
|
|
| |
statements in the post-handler for EQN in -mdoc and -man.
|
|
|
|
| |
the adding itself is implemented; equation data is not yet shown.
|
|
|
|
| |
place that it's called.
|
|
|
|
| |
ok kristaps@ jmc@.
|
|
|
|
|
| |
Inside .Bk or inside the SYNOPSIS, Unix variant macros cleared
the keep flag.
|
|
|
|
|
|
| |
keep flags before they are called.
Without this bugfix, .Bk was ineffective in some cases.
"looks reasonable" kristaps@
|
| |
|
| |
|
|
|
|
|
| |
directives. For now this will just ignore them (except for -Ttree,
which just notes that an EQN's been accepted).
|
|
|
|
|
|
|
|
| |
between EQ and EN roff blocks. EQN is different from TBL in that data
after .EQ is unilaterally considered an equation until an .EN. Thus,
there's no need to jump through hoops in having table spans and so on.
This is ONLY the parse code framework in libroff. EQN is not yet passed
into the backends.
|
|
|
|
| |
won't recognise them when invoked as e.g. `. TS' (we, however, do).
|
|
|
|
|
| |
shitty groff behaviour. Do the same, but raise a warning to this
effect. This from a TODO noted by schwarze@.
|
| |
|
|
|
|
|
|
|
| |
Don't use it in new manuals, it is inherently non-portable, but we
need it for backward-compatibility with existing manuals, for example
in Xenocara driver pages.
ok kristaps@ jmc@ and tested by Matthieu Herrb (matthieu at openbsd dot org)
|
|
|
|
| |
whitespace.
|
| |
|
|
|
|
| |
This removes a TODO raised by schwarze@.
|
| |
|
| |
|
|
|
|
| |
with "xxBSD-yy"
|
|
|
|
| |
ok kristaps@
|
|
|
|
|
|
|
| |
generate man(7) or mdoc(7) nodes for all these spans,
not only for the last one.
Restores the horizontal lines in the cpu(4/hppa) tables.
ok kristaps@
|
|
|
|
|
|
|
|
|
|
| |
Instead, let one line of input data add two new spans
to the tbl tree during one single call of tbl_data().
Note that this causes the horizontal line to get parsed
into the tbl tree, but not yet used in the output,
which will be fixed next.
Avoids data loss in cpu(4/hppa).
ok kristaps@
|
|
|
|
|
|
| |
correct alignment of centered cells
adjust horizontal rule width to the new spacing
ok kristaps@
|
| |
|
|
|
|
|
|
| |
for now. All of these just cause a bit too much or too little
whitespace, but no serious formatting problems.
Triggered by reports from brad@.
|
|
|
|
|
|
| |
on a UNIX system use UNIX conventions, and UNIX tools working
on them expect that.
ok jmc@
|
|
|
|
|
|
| |
As pointed out by Joerg Sonnenberger, this is useful
because we use mmap(3) and look for '\n' by hand.
"check it in" kristaps@
|
|
|
|
| |
ok jmc@.
|
| |
|
| |
|