- .Fn and .Fc now print a final semicolon (`;') after a
function declaration in the SYNOPSIS
- .%I implemented
- .At outputs ``AT&T UNIX'' if called without arguments
- minor cleanup
Obtained from: CSRG archives
One can now, for example, write:
.Sh EXAMPLES
Have you read the
.Xr mdoc 7 ?
.Pp
Do you like
.Fx ?
The mdoc.samples(7) page has been automatically updated to
record this change.
use of the .ne requests. groff(1) apparently inserts some virtual trap at
the end of each page, and this was causing the .ne request to output extra
lines. Solution is to only use them in troff mode.
Also fixed a related bug in .It macros, where it would insert a page break
in the middle of a sentence.
Removed the end of page trap in nroff mode, as this causes .sp requests to
sometimes eat the space due to the nearby trap.
Removed blank line that appeared as the first line on each nroff-formatted
manual page.
Obtained from: NetBSD
for function. For example: for stat(2) syscall (owned by libc) we will add
following code:
.Sh LIBRARY
.Lb libc
and it will be rendered to:
LIBRARY
Standard C Library (libc, -lc)
Suggested by: mpp
Idea obtained from: NetBSD
page of -mdoc manual pages in troff mode. The problem has been
introduced in rev 1.12; apparently ending a line inside a macro
definition with \c doesn't behave as Bill expected, and troff was
fooled to believe previous output was already pending thus a new page
needed to be emitted. Using a troff comment .\" instead of \c seems
to solve this, alas the brain^Wnice sed(1) magic needs to be taught to
_not_ strip those comments now.
I think -stable is not affected by this.
The .Fx macro was missing 2.1.7.
Add 2.2.5 to both .Os and .Fx. If I'm wrong about the version
number, no big deal - it can be removed later, but I wanted
to be able to get this into 2.2 so that when I'm using a
2.2 system ome months down the line, man pages intended for (what I
think will be the next 2.2 release) will be formatted properly.
Also fix a typo in a comment.
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
