| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
before even reparsing the expanded macro.
That is the least dirty way to fix the bug that \(.$ remained set
after execution of the user-defined macro ended. Any other way
to fix it would probably require changes to read.c, which really
shouldn't be bothered with such roff(7) internals.
|
| |
|
|
|
|
|
|
| |
It is not broken because of \), which is correctly implemented, but
the addition merely reveals a hidden bug elsewhere, almost certainly
in \\ handling. Given that \\ is among the most mysterious escape
sequences and using it is very strongly discouraged in manual pages,
fixing that is not urgent - and may be hard.
|
| |
|
|
|
| |
intentionally leave it undocumented. Abused for example in the
groff(7) manual page.
|
| |
|
|
|
|
| |
as groff, and also honour the explicit alignment indicator "\&".
This required an almost complete rewrite of both the measurement
function and the formatter function for numeric cells.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
roff conditional, except that the .char request still isn't supported
and that behaviour differs from groff in many edge cases.
But at least valid character names and numbers are now distinguished
from invalid ones.
This also fixes the bug that parsing of the 'c' conditional was
incomplete, which resulted in leaking the tested character to the
input parser at the beginning of the body when the condition was
inverted.
|
| |
|
|
| |
because that turned it into a bogus line continuation.
|
| |
|
|
| |
with comment); used for example by gropdf(1)
|
| | |
|
| |
|
|
| |
horizontally align the numbers in the same way as groff does.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
and in particular do not reset font mode.
|
| |
|
|
| |
if the first one is explicitly closed with .YS.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
to understand existing man(7) code and deleting parts that would only
be useful for writing new documents, which we strongly discourage:
* Delete the MANUAL STRUCTURE section which merely duplicates mdoc(7).
* Delete internal cross references only useful for writing new code.
* Delete many instances of "included only for compatibility" as the
whole language is only provided for compatibility.
* Fix a few minor errors and omissions.
|
| |
|
|
| |
used in most manual pages of the groff package
|
| |
|
|
|
| |
that is undefined according to the C standard. Robert Elz <kre at
munnari dot oz dot au> pointed out i wasn't quite done yet.
|
| |
|
|
| |
used for example by groff_diff(7)
|
| |
|
|
|
|
| |
a static array. Christos Zoulas, Robert Elz, and Andreas Gustafsson
point out that is undefined behaviour by the C standard even if we
never access the pointer.
|
| |
|
|
|
|
|
|
| |
While here, delete the section about predefined strings.
For manual pages, the concept is not important enough to be discussed
in such a prominent place, and some aspects of the text were also
misleading. Add a shorter version of the relevant parts to the
description of the \* escape sequence instead.
|
| |
|
|
|
| |
by allowing the preprocessor to pass it through to the formatters.
Used for example by the groff_char(7) manual page.
|
| |
|
|
| |
and provide a way to specify additional diff(1) options
|
| |
|
|
| |
found by Thomas Klausner <wiz at NetBSD> via a compiler warning
|
| |
|
|
|
| |
workaround in place for now for the benefit of older systems,
and other systems might contain similar problems.
|
| | |
|
| |
|
|
|
| |
latter is a NetBSD idiosyncrasy reported by wiz@. Also take into
account that NetBSD declares getsubopt(3) in the wrong header.
|
| |
|
|
| |
used for example in the ditroff(7) manual of the groff package
|
| | |
|
| |
|
|
| |
escape sequences, used for example in the groff_char(7) manual page
|
| |
|
|
|
| |
and some groff manual pages actually use them in .ft requests.
It's easy enough to handle these .ft requests in mandoc, too.
|
| |
|
|
|
| |
Examples of manual pages (ab)using it
include groff(7), chem(1), groff_mom(7), and groff_hdtbl(7).
|
| |
|
|
|
|
| |
don't respond with the lie: "No entry for chmod in the manual."
Instead, say "No entry for chmod in section 3 of the manual."
Came up after a question from kn@; OK kn@.
|
| | |
|
| | |
|
| |
|
|
|
| |
in general, when introducing the *typographic* term "hyphen",
actually display a real hyphen in output modes supporting it.
|
| |
|
|
|
|
| |
simplest and most important instructions together and at the
beginning. No text change.
Suggested by jmc@.
|
| |
|
|
|
|
|
|
|
|
| |
In some cases, it meant "render as an ASCII character in output
modes that have a notion of codepoints" (e.g. UTF-8, HTML); in other
cases, "render in the text font in output modes that also provide
a special font for mathematical symbols" (e.g. PostScript, PDF).
Also explicitly annotate the escape sequences that use a special
font if available.
OK bentley@
|
| |
|
|
|
|
|
|
| |
for hyphens and minus signs in manual pages.
Since there is consensus that a typographically perfect solution is
impossible, let's KISS - just write "-", don't bother with "\-", all
currently relevant manual page formatters can handle "-" reasonably.
OK jmc@ bentley@
|
| |
|
|
|
| |
the sheer number of issues is amazing,
but they all look feasible
|
| |
|
|
|
| |
string argument preceded a string argument beginning with "--".
Found by Leah Neukirchen <leah at vuxu dot org> with -Wpointer-compare.
|
| |
|
|
|
|
| |
the parse point to the beginning of the new buffer or we risk out
of bounds accesses. Bug found by Leah Neukirchen <leah at vuxu dot
org> with valgrind on Void Linux.
|
| |
|
|
|
| |
which occurred in situations like ".Fl a Cm --"; found by
Leah Neukirchen <leah at vuxu dot org> with valgrind on Void Linux.
|
| |
|
|
|
|
| |
autodetect whether the compiler can use -W and -static,
clearer output from ./configure,
and adjust some configuration instructions
|
| | |
|
| | |
|
