From: Tony Travis <tony.travis@minke-informatics.co.uk>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Welcome to new TUHS subscribers
Date: Sat, 12 Oct 2019 21:42:24 +0100 [thread overview]
Message-ID: <c8e1933a-cee7-c341-3d20-1834a02fdfce@minke-informatics.co.uk> (raw)
In-Reply-To: <ac06df0b-49c6-828e-e8a5-5c0500a7db84@gmail.com>
On 12/10/2019 20:39, Nemo Nusquam wrote:
> On 10/10/19 22: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...
>
> At the risk of being labelled a pedant. from the OED:
Hi, Nemo.
It takes one to know one!
> https://dictionary.cambridge.org/dictionary/english/acronym
What is interesting about this definition is that an 'acronym' is
pronounced as a word (i.e. not spelled out as letters). So, from that
point of view PDP-11 is an 'initialism' and not an acronym :-)
> https://dictionary.cambridge.org/dictionary/english/initialism
Which opens up a whole area of controversy about how to pronounce:
vi
In my experience, research users and hackers spell it out as "vee eye"
as originally described by Bill Joy, but business/enterprise users tend
to pronounce it as "vye" instead.
Well, I'm a research *nix user so I spell "vi" out, but my dark secret
is that I do pronounce "vim" as a full word and don't spell it out...
I suppose this is just about recognition of a suitable peer group that
agree, but it really sets my teeth on edge when people pronounce "vi"!
Anyone else got pet hates about how people pronounce *nix commands?
There are many pointless discussions about this already on the Internet,
so please only post comments here of historical interest like mine :-)
Bye,
Tony.
--
Minke Informatics Limited, Registered in Scotland - Company No. SC419028
Registered Office: 3 Donview, Bridge of Alford, AB33 8QJ, Scotland (UK)
tel. +44(0)19755 63548 http://minke-informatics.co.uk
mob. +44(0)7985 078324 mailto:tony.travis@minke-informatics.co.uk
next prev parent reply other threads:[~2019-10-12 20:42 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
2019-10-12 19:39 ` Nemo Nusquam
2019-10-12 20:42 ` Tony Travis [this message]
-- 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=c8e1933a-cee7-c341-3d20-1834a02fdfce@minke-informatics.co.uk \
--to=tony.travis@minke-informatics.co.uk \
--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).