From: random832@fastmail.com (Random832)
Subject: [TUHS] Slashes (was: MS-DOS)
Date: Fri, 08 Jul 2016 14:23:11 -0400 [thread overview]
Message-ID: <1468002191.3664013.660840929.6B8BA92D@webmail.messagingengine.com> (raw)
In-Reply-To: <CAC20D2NBP_SsjYRspmv8zwmFxg__w2mCrJOG0OBsB+u6M+GUPQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
On Fri, Jul 8, 2016, at 10:52, Clem Cole wrote:
> I can not speak for anyone else. But at the time when I was a part
> of the /usr/group UNIX standards** mtgs I personally do not believe I
> had ever heard of the term "solidus." Such a term maybe had been used
> in my first form Latin classes from the 1960s, but by the 1980s I had
> long ago forgotten any/all of my Latin. I certainly did not try to
> remember it as a computer professional.
>
> In those days many of us, including me, did (and still do) refer to
> the asterisk as "splat" and the exclamation point as "bang" from the
> sound made by them when they printed yellow oiled paper @ 10 cps from
> the console TTY. But slash was what we called the character that is
> now next to the shift key on modern keyboards. I do not remember
> ever using, much less needed to refer to, the character "back slash"
> until the unfortunate crap that the folks in Redmond forced on the
> industry.
You never had to use it for escaping in C/Regex/Troff/etc?
> Although interestingly enough, the vertical bar or UNIX "pipe" symbol
> was used and discussed freely in those days. I find it interesting
> that Redmond-ism became the unshifted character, not the vertical bar
> by the shear force of economics of the PC.
ASCII keyboards had \ unshifted long before the PC. The ASR-33 didn't
have it (it didn't have pipe at all - backslash was on shift-L), but
every DEC keyboard I can find did, as did the ADM-3a, and incidentally
the Symbolics Lisp Machine's keyboard.
I had suspected the reason that [\] ended up as the unshifted characters
is because {|} were not available on uppercase-only keyboards, but I
can't find any uppercase terminals that had separate keys for them (the
ASR-33 had them on shift- KLM). I expect that's also why ^, on shift-N,
was used for pipes rather than the vertical bar in the earliest versions
of Unix that had them.
What terminals did you use, back in those days?
(Incidentally, I can find *literally no* pictures of a Teletype 37,
and no sufficiently high-quality closeups of a 38 to determine its
keyboard layout)
next prev parent reply other threads:[~2016-07-08 18:23 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 14:52 Clem Cole
2016-07-08 14:59 ` Clem Cole
2016-07-08 15:47 ` Nemo
2016-07-08 16:31 ` Steffen Nurpmeso
2016-07-08 20:29 ` Clem Cole
2016-07-08 16:27 ` Steffen Nurpmeso
2016-07-08 18:00 ` Steve Nickolas
2016-07-08 18:23 ` Random832 [this message]
2016-07-08 20:49 ` Clem Cole
2016-07-08 21:09 ` Ron Natalie
2016-07-08 21:16 ` John Cowan
2016-07-08 21:45 ` Ron Natalie
2016-07-09 16:47 ` Dave Horsfall
2016-07-09 17:03 ` John Cowan
2016-07-09 17:21 ` Milo Velimirovic
2016-07-10 14:38 ` [TUHS] Slashes Christian Neukirchen
-- strict thread matches above, loose matches on Subject: below --
2016-07-10 1:41 [TUHS] Slashes (was: MS-DOS) Norman Wilson
2016-07-10 1:46 ` Steve Nickolas
2016-07-10 1:52 ` John Cowan
2016-07-12 17:53 ` Tim Bradshaw
2016-07-12 18:05 ` Ronald Natalie
2016-07-13 9:24 ` Wesley Parish
2016-07-13 10:09 ` Joerg Schilling
2016-07-10 21:10 ` Sven Mascheck
2016-07-08 17:36 Norman Wilson
2016-07-08 11:25 Norman Wilson
2016-07-08 13:16 ` John Cowan
2016-07-08 14:06 ` Brantley Coile
2016-07-02 0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02 1:13 ` Steve Nickolas
2016-07-07 5:02 ` [TUHS] Slashes (was: MS-DOS) Greg 'groggy' Lehey
2016-07-07 13:43 ` Nemo
2016-07-07 14:11 ` John Cowan
2016-07-07 14:18 ` Steffen Nurpmeso
2016-07-07 23:47 ` Greg 'groggy' Lehey
2016-07-08 5:40 ` scj
2016-07-08 7:06 ` Greg 'groggy' Lehey
2016-07-08 11:09 ` Steffen Nurpmeso
2016-07-09 0:03 ` Greg 'groggy' Lehey
2016-07-09 14:24 ` Steffen Nurpmeso
2016-07-09 16:38 ` John Cowan
2016-07-11 11:20 ` Tony Finch
2016-07-11 11:54 ` Nemo
2016-07-11 13:15 ` Joerg Schilling
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=1468002191.3664013.660840929.6B8BA92D@webmail.messagingengine.com \
--to=random832@fastmail.com \
/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).