From: arnold@skeeve.com
To: ron@ronnatalie.com, arnold@skeeve.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Speaking commands [Was: Bell System Technical Journal archive]
Date: Tue, 17 Jul 2018 21:54:02 -0600 [thread overview]
Message-ID: <201807180354.w6I3s2Bl001828@freefriends.org> (raw)
In-Reply-To: <FE1CC6AF-1B71-4B97-9B1A-96EFD601DB91@ronnatalie.com>
That was Ken Thompson who said that. And indeed, in Plan 9 it's called
"create".
Arnold
Ron Natalie <ron@ronnatalie.com> wrote:
> There was a quote going around where when asked if he would do anything differently, he said he’d put an e on the end of creat. I guess he was tire of people calling it Cree-at.
>
> Sent from my iPhone
>
> > On Jul 17, 2018, at 8:20 AM, arnold@skeeve.com wrote:
> >
> > Nemo <cym224@gmail.com> wrote:
> >
> >> I was intrigued by BMK's comment that "ed" was never spokend as "ed"
> >> by "those in the know", which leads me to wonder how things were
> >> spoken.
> >
> > I always spelled out the two-letter commands: e-d, a-r, l-s, r-m, c-p.
> > chmod I pronounced as ch-mod (not mode), but 'rmdir' was 'remove dir'
> > and for some reason, mv was move. (I think the doc for vi officially
> > stated that the proram's name was to be pronounced v-i and not 'vie'.)
> >
> > Undoubtedly there were many regional differences... :-)
> >
> > Arnold
>
prev parent reply other threads:[~2018-07-18 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:33 Nemo
2018-07-17 13:20 ` arnold
2018-07-17 14:39 ` John P. Linderman
2018-07-18 17:39 ` arnold
2018-07-19 4:59 ` [TUHS] ar libraries [was: Speaking commands [Was: Bell System Technical Journal archive]] Greg 'groggy' Lehey
2018-07-19 15:29 ` Paul Winalski
2018-07-19 16:12 ` John P. Linderman
2018-07-20 23:01 ` [TUHS] Speaking commands [Was: Bell System Technical Journal archive] Kurt H Maier
2018-07-18 0:56 ` Ron Natalie
2018-07-18 3:54 ` arnold [this message]
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=201807180354.w6I3s2Bl001828@freefriends.org \
--to=arnold@skeeve.com \
--cc=ron@ronnatalie.com \
--cc=tuhs@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).