From: Rob Pike <robpike@gmail.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] The Unix shell: a 50-year view - hopefully final review of letter
Date: Sun, 11 Jul 2021 07:55:12 +1000 [thread overview]
Message-ID: <CAKzdPgy-eCpPitDM6DBkJFNvCTPMQKrVC-pXVjTFaOoVdbnFTA@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgyOVJk+d-N6H8Gtyy4P4wzczpEP1VpwXORFERV=R=qafw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
(There were some ™'s in there too.)
On Sun, Jul 11, 2021 at 7:54 AM Rob Pike <robpike@gmail.com> wrote:
> Yes, a related issue came up when dmr rebelled when the lawyers made him
> rewrite a phrase when reprinting a paper in the BSTJ. For some reason, he
> didn't prefer the rewrite: "PDP-11 computer system UNIX system file system".
>
> -rob
>
>
> On Sun, Jul 11, 2021 at 6:12 AM Jon Steinhart <jon@fourwinds.com> wrote:
>
>> 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.
>>
>
[-- Attachment #2: Type: text/html, Size: 1726 bytes --]
next prev parent reply other threads:[~2021-07-10 21:56 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
2021-07-10 21:54 ` Rob Pike
2021-07-10 21:55 ` Rob Pike [this message]
-- 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=CAKzdPgy-eCpPitDM6DBkJFNvCTPMQKrVC-pXVjTFaOoVdbnFTA@mail.gmail.com \
--to=robpike@gmail.com \
--cc=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).