From: Jon Steinhart <jon@fourwinds.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] The Unix shell: a 50-year view - hopefully final review of letter
Date: Sat, 10 Jul 2021 13:11:36 -0700 [thread overview]
Message-ID: <202107102011.16AKBaVh2824331@darkstar.fourwinds.com> (raw)
In-Reply-To: <CMM.0.95.0.1625947754.beebe@gamma.math.utah.edu>
Nelson H. F. Beebe writes:
> Jon Steinhart writes
>
> > I use UNIX instead of Unix as that's what I believe is the correct form.
>
> Brian Kernighan addresses this issue in section 7.3 of his
> recent memoir: it has "UNIX A History and a Memoir" on the
> cover, but prefers "Unix" in the rest of that book, except
> in the noted section. He also refers back to the 1984
> book with Rob Pike, "The UNIX Programming Environment",
> in which the typography uses small caps for "UNIX".
Yeah, small caps was what I always considered correct.
next prev parent reply other threads:[~2021-07-10 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 20:02 Noel Chiappa
2021-07-10 20:09 ` Nelson H. F. Beebe
2021-07-10 20:11 ` Jon Steinhart [this message]
2021-07-10 21:54 ` Rob Pike
2021-07-10 21:55 ` Rob Pike
-- strict thread matches above, loose matches on Subject: below --
2021-07-10 19:18 Jon Steinhart
2021-07-10 19:27 ` Rich Morin
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=202107102011.16AKBaVh2824331@darkstar.fourwinds.com \
--to=jon@fourwinds.com \
--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).