| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
partial explicit macros. Leah Neukirchen <leah at vuxu dot org>
rightfully points out that the check makes no sense for these macros.
|
|
|
|
|
|
|
|
|
| |
across output devices, counter-intuitive, and resulted in ugly
output for many real-world manual pages. Always format even long
links in-line. I already committed a similar change to groff.
OK jmc@, bentley@, and the original author
of the feature, Werner Lemberg <wl@gnu.org>.
|
| |
|
|
|
|
|
|
|
| |
even if other arguments precede -column. This is required because
the .It parser needs to know whether or not we are a -column list.
Fixes tree corruption leading to an assertion failure.
Bug reported by bentley@.
|
| |
|
|
|
|
|
| |
to do things differently in the ps vs pdf case;
from espie@
|
|
|
|
| |
from jca@, ok jmc@
|
|
|
|
|
|
|
|
| |
by using PostScript as a programming language.
* Define and use one PostScript procedure to select each font.
* Define and use procedures combining "use" and "show".
* In one of these, reuse the current row if it did not change.
Most ideas and most coding by espie@, tweaked by me.
|
|
|
|
|
|
|
|
|
| |
and use the setpagedevice PostScript operator to help printers
automatically select the paper of the best matching PageSize.
Many thanks to Mike Williams <obsd1 at eandem dot co dot uk>
for teaching me about the relevant features of PostScript and DSC
and for suggesting what to put into the first %%DocumentMedia argument.
|
| |
|
|
|
|
| |
basic units, also slightly more precise
|
|
|
|
|
|
|
|
|
|
|
| |
last call writing to it is always ps_endline(), which ends with
ps_pclose(), which prints "ET" (end text).
Consequently, do not print another instance of "ET" in ps_closepage()
after the footer line and before the "endstream" for the page.
Fixing a PDF syntax error found while investigating the bug report
from Jan Stary that also resulted in the previous commit.
|
|
|
|
|
|
|
| |
Resource objects, and the Catalog object, fixing three PDF syntax
errors that were present in every PDF file generated with mandoc
since the initial checkin of the formatter in July 2010.
Bug reported by Jan Stary <hans at stare dot cz> on misc@.
|
|
|
|
|
|
|
|
|
|
|
|
| |
I looked through our whole tree and failed to find a single use
that is really convincing, except those with .Mt. Putting it around
character and key names is somewhat widespread and maybe acceptable,
even if hardly useful.
So for now, delete the bogus examples and explain what these macros
are really used for. Discourage the most common abuses.
Triggered by a question from Raf Czlonka <rczlonka at gmail dot com>.
|
| |
|
|
|
|
|
| |
an architecture argument and the second with an invalid one.
Bug found by jsg@ with afl(1).
|
| |
|
|
|
|
|
| |
could be triggered with '.SS ""';
reported by Michael <Stapelberg at debian>
|
| |
|
| |
|
|
|
|
| |
Bug pointed out by tedu@.
|
|
|
|
|
|
| |
compare the files directly, allowing a much stricter pledge(2), at
very little cost: merely 15 additional lines of very simple code.
Suggested by George Brown <321 dot george at gmail dot com> on misc@.
|
|
|
|
|
|
|
|
|
| |
one file and exactly one directory to remove. While here, increase
the size of the buffer such that the file name actually fits.
Minus 17 lines of code, no functional change.
Opportunity for simplification reported by George Brown <321 dot
george at gmail dot com> on misc@.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
One benefit is a reduced probablity that a blank appears between
a function name and the opening parenthesis introducing the arguments.
The heuristics isn't perfect and may occasionally suppress a blank
that wouldn't do harm.
|
|
|
|
|
| |
that can be changed unilaterally because groff fails to render them
at all.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
letters as in groff commit babca15f from trying to imitate the
characters' graphical shapes, which resulted in unintelligible
renderings in many cases, to transliterations conveying the characters'
meanings. One benefit is making these characters usable for portable
manual pages.
Solving a problem pointed out by bentley@.
|
|
|
|
| |
of MLINKS. Inaccuracy pointed out by espie@.
|
|
|
|
|
| |
print a meaningful warning and skip the entry.
Issue reported by espie@.
|
|
|
|
|
|
|
|
|
| |
any more input files, and it would be misleading to start a parser,
because that would show randomly truncated text.
Instead, print an error message and exit the program.
Issue found by Leah Neukirchen <leah at vuxu dot org>, who was
surprised to see half a manpage when her /tmp/ overflew.
|
|
|
|
| |
suggested by Sevan Janiyan <venture37 at geeklan dot co dot uk>
|
|
|
|
| |
was probably copied from mandoc(1) or apropos(1), where it is true.
|
| |
|
|
|
|
|
|
| |
in the last two letters of the last word of the sentence.
No false positives in base or Xenocara.
Suggested by and OK jmc@.
|
|
|
|
| |
Feedback and OK jmc@.
|
|
|
|
|
|
|
| |
pager, and how to remove markup. Add related cross references.
While here, as suggested by jmc@, replace the excessive cross
references to the intro pages by a more relevant one to mandoc(1).
Triggered by a question from, using feedback from, and OK jmc@.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for man(1) lookup. For OpenBSD base and Xenocara, that functionality
was never intended to be required, and i just fixed the last handful
of offenders using it - not counting the horribly ill-designed
interfaces engine(3) and lh_new(3) which are impossible to properly
document in the first place.
Of course, apropos(1) and whatis(1) continue to use SYNOPSIS .Nm,
.Fn, and .Fo macros, so "man -k ENGINE_get_load_privkey_function"
still works.
This change also gets rid of a few bogus warnings "cross reference
to self" which actually are *not* to self, like in yp(8).
This former functionality was intended to help third-party software
in the ports tree and on non-OpenBSD systems containing manual pages
with incomplete or corrupt NAME sections. But it turned out it did
more harm than good, and caused more confusion than relief,
specifically for third party manuals and for maintainers of
mandoc-portable on other operating systems. So kill it.
Problems reported, among others, by Yuri Pankov (illumos).
OK jmc@
|
|
|
|
|
| |
wrapping around to huge numbers and risking memory exhaustion;
fixes Debian ps(1). Bug reported by Dr. Markus Waldeck.
|
|
|
|
|
|
|
| |
segfaults on certain hardened versions of glibc. Triggered by .sp
or blank lines right before .SS or .SH, or before the first .Sh.
Found the hard way by Dr. Markus Waldner on Debian
and by Leah Neukirchen on Void Linux.
|
| |
|
|
|
|
|
|
| |
the enum constant was forgotten in this call. No functional change
since the mmsg argument is NULL anyway.
Found by florian@ with clang.
|
|
|
|
| |
patch from florian@, found with clang
|
|
|
|
| |
it causes too much trouble on non-OpenBSD systems
|
|
|
|
| |
and it is causing too much trouble in -portable.
|