The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: tuhs@minnie.tuhs.org, groff@gnu.org
Subject: [TUHS] [TUHS/groff] Provenance of .SB macro in man pages
Date: Sun, 26 Jan 2020 02:00:13 +1100	[thread overview]
Message-ID: <20200125150010.dwqpgs5upkmuoleu@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]

Hi folks,

I've been adding a history subsection to the groff_man(7) page for the
next groff release (date TBD) and thanks to the TUHS archives I've been
able to answer almost all the questions I had about the origins of the
man(7) language's macros and registers (number and string).

I'm inlining my findings in rendered and source form below, but there's
one feature I haven't been able to sort out--where did .SB (small bold)
come from?  The oldest groff release I can find online is 1.02 (June
1991), and .SB is already there, but I can't find it anywhere else.  Is
it a GNUism?  Did it perhaps appear in a proprietary Unix first?

I'm aware of Kristaps Dzonsons's history of Unix man pages[1], but
unfortunately for me that is more of a history of the *roff system(s),
and does not have much detail about the evolution of the man(7) macro
language itself.

If you can shed any light on this, I'd appreciate it!

   History
       Version 7 Unix (1979) supported all of the macros described in this
       page not listed as extensions, except .P, .SB, and the deprecated .AT
       and .UC.  The only string registers defined were R and S; no number
       registers were documented.  .UC appeared in 3BSD (1980) and .P in AT&T
       Unix System III (1980).  4BSD (1980) added lq and rq string registers.
       4.3BSD (1986) added .AT and AT&T's .P.  DEC Ultrix 11 (1988) added the
       Tm string register.

.\" ====================================================================
.SS History
.\" ====================================================================
.
Version\~7 Unix (1979) supported all of the macros described in this
page not listed as extensions,
except
.BR .P ,
.BR .SB ,
.\" .SS was implemented in tmac.an but not documented in man(7).
and the deprecated
.BR .AT
and
.BR .UC .
.
The only string registers defined were
.B R
and
.BR S ;
no number registers were documented.
.
.B .UC
appeared in 3BSD (1980) and
.B .P
in AT&T Unix System\~III (1980).
.
4BSD (1980) added
.\" undocumented .VS and .VE macros to mark regions with 12-point box
.\" rules (\[br]) as margin characters, as well as...
.B lq
and
.B rq
string registers.
.
4.3BSD (1986) added
.\" undocumented .DS and .DE macros for "displays", which are .RS/.RE
.\" wrappers with filling disabled and vertical space of 1v before and
.\" .5v after, as well as...
.B .AT
and
AT&T's
.BR .P .
.
DEC Ultrix\~11 (1988) added the
.B Tm
string register.
.
.\" TODO: Determine provenance of .SB.

Regards,
Branden

[1] https://manpages.bsd.lv/history.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2020-01-25 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 15:00 G. Branden Robinson [this message]
2020-01-25 19:13 ` reed
2020-01-25 19:36   ` G. Branden Robinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200125150010.dwqpgs5upkmuoleu@localhost.localdomain \
    --to=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).