From: Michael Parson <mparson@bl.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Welcome to new TUHS subscribers
Date: Fri, 11 Oct 2019 08:11:08 -0500 [thread overview]
Message-ID: <4c1973ab965afdcc938cbb7dca913427@bl.org> (raw)
In-Reply-To: <a0a5fc29-1ae4-9b00-5207-072903365a6e@minke-informatics.co.uk>
On 2019-10-11 07:55, Tony Travis wrote:
> On 11/10/2019 03:46, Dave Horsfall wrote:
>> On Thu, 10 Oct 2019, Noel Chiappa wrote:
>>
>>> DEC documentation mostly used uppercase in the text; e.g. the "pdp11
>>> peripherals handbook" (to transcribe the cover exactly) uses "PDP-11"
>>> several times on pg 1-1.
>>
>> And being an acronym it is of course upper-case...
>
> Hi, Dave.
>
> On the _machine_ itself, DEC wrote "pdp11"...
Well, that's also in-line with their using all lower-case on their logo.
> An acronym doesn't have to be upper-case!
>
> Many Unix commands are lower case acronyms:
>
> cd = (c)ange (d)irectory
> pwd (p)rint (w)orking (directory)
> ls = (l)ist file(s)
I always thought of it as (l)i(s)t files.
> I guess that my introduction to Seventh Edition Unix running on a
> "pdp11/34" made me think it was obviously designed to run Unix ;-)
>
> Bye,
>
> Tony.
--
Michael Parson
Pflugerville, TX
KF5LGQ
next prev parent reply other threads:[~2019-10-11 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 13:18 Noel Chiappa
2019-10-11 2:46 ` Dave Horsfall
2019-10-11 12:55 ` Tony Travis
2019-10-11 13:11 ` Michael Parson [this message]
2019-10-12 19:39 ` Nemo Nusquam
2019-10-12 20:42 ` Tony Travis
-- strict thread matches above, loose matches on Subject: below --
2019-10-09 20:13 Warren Toomey
2019-10-09 20:50 ` Tomasz Rola
2019-10-09 23:26 ` Dave Horsfall
2019-10-09 23:51 ` Warren Toomey
2019-10-10 0:03 ` Dave Horsfall
2019-10-10 0:22 ` greg travis
2019-10-09 23:58 ` Greg 'groggy' Lehey
2019-10-10 9:21 ` Tony Travis
2019-10-10 15:27 ` Larry W. Cashdollar via TUHS
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=4c1973ab965afdcc938cbb7dca913427@bl.org \
--to=mparson@bl.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).