| Age | Commit message (Collapse) | Author |
|---|
|
ok sthen florian
|
|
|
|
|
|
OK mpi@
|
|
|
|
I flew from there to Xi'an in 2019.
|
|
OK cheloha@
|
|
existing interface to its default state", because it doesn't. ok jmc@
|
|
my parents.
|
|
|
|
where I landed and departed at one of the
two gates to have a great time in the Ural last year.
|
|
|
|
|
|
|
|
wrong parsing class ESCAPE_SPECIAL to the better-suited parsing class
ESCAPE_UNDEF, exactly like it is already done for the similar \\,
which isn't a character escape sequence either.
No formatting change is intended just yet, but this will matter for
upcoming improvements in the parser for roff(7) macro, string, and
register names.
See the node "5.23.2 Copy Mode" in "info groff" regarding
what \\ and \. really mean.
|
|
semantics (test identifier for syntactical validity), not at all
following the completely unrelated Heirloom semantics (define
hyperlink target position).
The main motivation for providing this implementation is to get \A
into the parsing class ESCAPE_EXPAND that corresponds to groff parsing
behaviour, which is quite similar to the \B escape sequence (test
numerical expression for syntactical validity). This is likely
to improve parsing of nested escape sequences in the future.
Validation isn't perfect yet. In particular, this implementation
rejects \A arguments containing some escape sequences that groff
allows to slip through. But that is unlikely to cause trouble even
in documents using \A for non-trivial purposes. Rejecting the nested
escapes in question might even improve robustnest because the rejected
names are unlikely to really be usable for practical purposes - no
matter that groff dubiously considers them syntactically valid.
|
|
escape sequence into the correct parsing class, ESCAPE_EXPAND.
Expansion of \g is supposed to work exactly like the expansion
of the related escape sequence \n (interpolate register value),
but since we ignore the .af (assign output format) request,
we just interpolate an empty string to replace the \g sequence.
Surprising as it may seem, this actually makes a formatting difference
for deviate input like ".O\gNx" which used to raise bogus "escaped
character not allowed in a name" and "skipping unknown macro" errors
and printed nothing, whereas now it correctly prints "OpenBSD".
|
|
escape sequence. This is needed to get \V into the correct parsing
class, ESCAPE_EXPAND.
It is intentional that mandoc(1) output is *not* influenced by environment
variables, so interpolate the name of the variable with some decorating
punctuation rather than interpolating its value.
|
|
|
|
ok sthen
|
|
from Raf Czlonka
|
|
before running rc_rcexec.
Based on an proposal from openbsd.tech at aisha.cc
ok robert@ abieber@
|
|
|
|
from "ignore" to "unsupported" because when an input file uses it,
mandoc(1) is likely to significantly misformat the output,
usually showing parts of the output in a different order
than the author intended.
|
|
|
|
|
|
help robert ajacoutot
ok ajacoutot
|
|
there are still a few odds and ends which should make their way to the
rest of the manpage eventually (or to the faq), useful information that's
not immediately available elsewhere
|
|
from Brad
|
|
|
|
|
|
|
|
default type of PF rule) don't allow ICMP responses unless they match an
existing state - tweak "keep state (sloppy)" to suggest from the first
sentence of the paragraph that it affects more than TCP. ok sashan@ bluhm@
|
|
OK @bluhm
|
|
|
|
OK tedu@
|
|
Make refcnt_rele() and refcnt_finalize() order memory operations so that
preceding loads and stores happen before 1->0 transition. Also ensure
that loads and stores that depend on the transition really begin only
after the transition has occurred. Otherwise the object destructor might
not see the object's latest state.
OK bluhm@
|
|
from Brad
|
|
|
|
|
|
|
|
custom implementation that only allowed matching all files in a
directory.
ok millert
|
|
|
|
the kstat api is a small part of implementing a kstat, most of it
depends on how you set up the kstat struct.
|
|
we did want it, so it's there and documented.
|
|
|
|
|
|
tree should be about on par with release(8)
okay schwarze@, sthen@
|
|
Document gi-docgen which is coming to gnome.port.mk soon.
|
|
|
