Age | Commit message (Collapse) | Author |
|
The last name of the author of groff is "Clark".
|
|
received from Douglas McIlroy in private mail:
https://manpages.bsd.lv/history/mcilroy_26_10_2020.txt
|
|
noticed by Werner himself on <groff at gnu dot org>;
while here, add missing .An macros
|
|
|
|
OK stsp@
|
|
I intended to commit this after the arch is enabled,
but jmc@ requests it right now.
|
|
manual pages document the same content, comparing can occasionally help
in cases of doubt, and some people may prefer one style, some the other.
While here, modernize a few .Lks from http:// to https://.
OK jmc@
|
|
feedback and okay schwarze@
|
|
|
|
We already supported "beta" releases but not "alpha", probably to
discourage people from pushing "alpha-quality" software in the ports
tree.
We have 30 ports with distfiles matching "alpha", and people just work
around the lack of explicit support for "alpha" releases with mixes of
crafted PKGNAME and REVISION/EPOCH. This looks needlessly complicated
and a bit unfair when compared to GH_COMMIT support.
Pointers from landry@ and sthen@, lgtm landry@, no objection from espie@
|
|
Whith lots of help from sthen@, espie@ and jca@
ok espie@ jca@
|
|
because we only retain the language for backward compatibility in
the first place. Part of the research done by <G dot Branden dot
Robinson at gmail dot com>, see the list <groff at gnu dot org> for
details.
No change to the following conventions: Consider portable whatever
made it into GNU troff no later than 4.4BSD. For portable extensions,
mention their origin at the end of the description. For non-portable
extensions, for example from man-ext, usually warn earlier, near
the beginning of the description.
|
|
Triggered by a question from Jason A. Donenfeld.
While here, delete three COMPATIBILITY entries that i fixed some time ago.
|
|
Noticed because Branden Robinson worked on related documentation in groff.
|
|
ok schwarze@
|
|
|
|
'default' class; also added to _PATH_DEFPATH in 2019. Update PATH accordingly.
OK millert@
|
|
as defining a term. Please only use it when automatic tagging does
not work. Manual page authors will not be required to add the new
macro; using it remains optional. HTML output is still rudimentary
in this version and will be polished later.
Thanks to kn@ for reminding me that i have been considering since
BSDCan 2014 whether something like this might be useful. Given
that possibilities of making automatic tagging better are running
out and there are still several situations where automatic tagging
cannot do the job, i think the time is now ripe.
Feedback and no objection from millert@; OK espie@ inoguchi@ kn@.
|
|
Change several instances, most of them to the usual -width Ds.
|
|
Closing a gap reported by bentley@, who also sent a patch,
but i'm explaining it somewhat differently.
While here, remove duplicate information from the text.
OK bentley@
|
|
|
|
similar to a diff sent in by <Masanori dot Ogino at gmail dot com>,
but using the up-to-date reference rather than one from 30 years ago;
OK jmc@
|
|
The DST and TIMEZONE options(4) are incompatible with KARL, so we need
some other way to compensate for an RTC running with a known offset.
Enter kern.utc_offset, an offset in minutes East of UTC. TIMEZONE has
always been minutes West, but this is inconsistent with how everyone
else talks about timezones, hence the flip.
TIMEZONE has the advantage of being compiled into the binary. Our new
sysctl(2) has no such luck, so it needs to be set as early as possible
in boot, from sysctl.conf(5), so we can correct the kernel clock from
the RTC's local time to UTC before daemons like ntpd(8) and cron(8)
start. To encourage this, kern.utc_offset is made immutable after the
securelevel(7) is raised to 1.
Prompted by yasuoka@. Discussed with deraadt@, kettenis@, yasuoka@.
Additional testing by yasuoka@.
ok deraadt@, yasuoka@
|
|
does exist -- execv(3). Still call this a family but without "Nm".
Adjust Xr in various pages to refer to the precise function used
rather than the family, in most cases the semantics of execve(2) are
being referenced, so change the Xr.
ok jmc
|
|
|
|
missing info reported by Ian <ropers at gmail dot com> on misc@
|
|
and only got adopted by GNU two decades later.
Thanks to Doug McIlroy <doug at cs dot dartmouth dot edu>
for pointing out the error.
|
|
suggested by Michal Nowak <mnowak at startmail dot com>
|
|
ok jmc@ schwarze@
|
|
|
|
from Jesper Wallin
|
|
which was removed in libc/asr/asr.c rev. 1.50 in 2015.
Smaller version of a patch
posted by Hiltjo Posthuma <hiltjo at codemadness dot org>.
No objection was raised when shown on tech@.
|
|
ok kettenis
|
|
suggested by deraadt; OK jmc
|
|
triggered by a question from Fabio Scotoni
|
|
triggered by a question from Fabio Scotoni <fabio at esse dot ch>
|
|
Fabio Scotoni <fabio at esse dot ch> reported it was missing in eqn(7)
|
|
Jan Stary <hans at stare dot cz> found it in an ancient groffer(1)
manual page (version 1.19) on MacOS X Mojave.
Having .break not implemented wasn't a particularly bright idea
because obviously, it tended to cause infinite loops.
|
|
for hyphen-minus, soften the language a bit: writing \- for it is
not wrong, and people started sending us patches to replace \- with '-'
in existing manual pages, which is not a worthwhile change unless
the \- is used at a place where it doesn't belong.
OK jmc@
|
|
|
|
Instead, use a tagged list and the canonical .Ic macro
as it is natural for such purposes.
While here, also delete heaps of needless escaping.
|
|
|
|
in UTF-8 output; suggested by bentley@
|
|
ok schwarze@
|
|
.Bd ... -compact
is better written as
.Bd ...
|
|
In facts, i works very similarly to .Em and .Sy.
Triggered by a question from Kurt Mosiejczuk <kurt at cranky dot work>.
|
|
|
|
rather than in the man(7) parser and formatters, document them in the
roff(7) manual, where they belong, rather than in the man(7) manual.
Mention that they imply an output line break, and mention which macros
imply these requests.
|
|
since these are clearly commands in a domain-specific language. As
a nice side effect, the resulting list allows including the synopsis
for each macro in the item head, reducing some repetitive verbiage.
|
|
The macros .Ql, .Dl, and .Bd -literal leave no room for any
valid use case for .Li whatsoever.
General direction discussed with jmc@.
|