The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] Slashes (was: MS-DOS)
@ 2016-07-08 14:52 Clem Cole
  2016-07-08 14:59 ` Clem Cole
                   ` (5 more replies)
  0 siblings, 6 replies; 42+ messages in thread
From: Clem Cole @ 2016-07-08 14:52 UTC (permalink / raw)


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3402 bytes --]

On Fri, Jul 8, 2016 at 7:09 AM, Steffen Nurpmeso <steffen at sdaoden.eu> wrote:

> ...and that actually makes me wonder why the engineers that
> created what became POSIX preferred slash instead
>
​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.   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.

Clem

** For those that do not know (my apologies to those that do) the 1985
/usr/group standards committee was the forerunner to IEEE P1003.  Which we
published as the first "official UNIX API standard agreed by the community"
(I still have a hardcopy).  But neither /usr/group nor USENIX had the
political authority to bring an official standard to FIPS, ANSI, ECMA, ISO
or like, while IEEE did.  So a few months before the last meeting, Jim
Issak petitioned IEEE for standards status, and the last meeting of the
/usr/group UNIX standards meeting was very short -- about 10 minutes.   We
voted to disband and then everyone in the room officially reformed a few
minutes later all signing in as IEEE P1003, later to be called POSIX.  For
further historical note, I was a "founding member" of both groups and the
editor of a number of early drafts (numbers 5-11 IIRC), as well as the
primary author of the Tape Format and Terminal I/O sections of P1003.1.
With Keith Bostic, I would later be part of the P1003.2 and pen the
original PAX compromise.  After that whole mess I was so disgusted with the
politics of the effort, I stopping going to the POSIX mtgs.

PPS While I did not work for them at the time, you can blame DEC for the
mess with the case/character sets in the POSIX & FIPS standards.   A number
of the compromises in the standard documents were forced by VMS, 7-bit
(case insensitivity) being the prime one.   While we did get in the
rational section of document that it was suggested/advised that systems
implementations and applications code be case insensitive and 8 bit clean
so that other character sets could be supported.  However the DEC folks
were firmly against anything more than 7-bit ASCII and supporting anything
in that character set. My memory is that the IBM folks were silent at the
time and just let the DEC guys carry the torch for 1960's 7-bit US English.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160708/fdf012d6/attachment-0001.html>


^ permalink raw reply	[flat|nested] 42+ messages in thread
* [TUHS] Slashes (was: MS-DOS)
@ 2016-07-10  1:41 Norman Wilson
  2016-07-10  1:46 ` Steve Nickolas
  2016-07-10 21:10 ` Sven Mascheck
  0 siblings, 2 replies; 42+ messages in thread
From: Norman Wilson @ 2016-07-10  1:41 UTC (permalink / raw)


Dave Horsfall:

  I still remember when the pipe command was "^" (pointy hat).

====

I still remember--barely--when \136 was up-arrow, not carat!

I don't think pipe was ever only ^, but that ^ was a
synonym for | added to make it easier to use on older
upper-case terminals that had no |.  Those (remaining
few) who were there at the time can perhaps clarify.

I still habitually quote shell arguments containing ^,
even though I haven't used a shell that required that
since late 1984 (Rob had removed the special meaning
from /bin/sh before I arrived at Bell Labs).  On the
other hand, I still cannot be bothered to get used to
quoting arguments containing !; I just disable all
that history and editing bloatware whenever possible.

Norman Wilson
Toronto ON


^ permalink raw reply	[flat|nested] 42+ messages in thread
* [TUHS] Slashes (was: MS-DOS)
@ 2016-07-08 17:36 Norman Wilson
  0 siblings, 0 replies; 42+ messages in thread
From: Norman Wilson @ 2016-07-08 17:36 UTC (permalink / raw)


Clem Cole:

  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.

=====

Oh, come on.  You programmed in C.  You probably used
UNIX back when @ was the default kill character (though
I doubt you're odd enough still to use that kill character,
as I do).  You surely used troff, LaTeX, or both, and have
doubtless sworn at regular expressions more often than
most of the young Linux crowd have had chocolate bars.

I think you've just forgotten it out of PBSD (post-backlash
stress disorder, nothing to do with Berkeley).

Norman Wilson
Toronto ON
UNIX\(tm old fart who swore at a regexp just yesterday


^ permalink raw reply	[flat|nested] 42+ messages in thread
* [TUHS] Slashes (was: MS-DOS)
@ 2016-07-08 11:25 Norman Wilson
  2016-07-08 13:16 ` John Cowan
  0 siblings, 1 reply; 42+ messages in thread
From: Norman Wilson @ 2016-07-08 11:25 UTC (permalink / raw)


Steffen Nurpmeso:

  ...and that actually makes me wonder why the engineers that
  created what became POSIX preferred slash instead -- i hope it is
  not the proud of high skills in using (maybe light) sabers that
  some people of the engineer community seem to foster.  But it
  could be the sober truth.  Or, it could be a bug caused by
  inconsideration.  And that seems very likely now.

====

It had nothing to do with engineers.  `Slash' for / has been
conventional American usage for as long as I can remember,
dating back well before POSIX or UNIX or the movie that made
a meme of light sabers.

It's unclear exactly how far back it dates.  The earliest
OED citation for `slash' as `A thin sloping line, thus /'
is dated 1961; but the cite is from Webster's 3rd.

Given the amount of violence prevalent in American metaphor,
it is hardly noteworthy.

Make American Language Violent Again (and I HATE MOSQUITOS*).

Norman Wilson
Toronto ON

* If you don't know what this refers to, you probably don't
want to know.


^ permalink raw reply	[flat|nested] 42+ messages in thread
* [TUHS] MS-DOS
@ 2016-07-02  0:12 Norman Wilson
  2016-07-02  1:13 ` Steve Nickolas
  0 siblings, 1 reply; 42+ messages in thread
From: Norman Wilson @ 2016-07-02  0:12 UTC (permalink / raw)


I suspect Yanks being pedantic about `slash' versus `forward slash'
would give an Englishman a stroke.

If that's too oblique for some of you, I can't help.

Norman Wilson
Toronto ON


^ permalink raw reply	[flat|nested] 42+ messages in thread

end of thread, other threads:[~2016-07-13 10:09 UTC | newest]

Thread overview: 42+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-07-08 14:52 [TUHS] Slashes (was: MS-DOS) 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
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

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).