From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Dash options
Date: Tue, 28 Nov 2017 13:20:41 -0500 [thread overview]
Message-ID: <CAC20D2MKRgpgiDaG6VtAM=qcuCPf89M-3fRfREQ=SAbC5+SAiw@mail.gmail.com> (raw)
In-Reply-To: <20171128131942.6705918C092@mercury.lcs.mit.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
dash as switches were always explained to me as from Multics. Having used
DEC systems, Univax and IBM systems originally with cards and ASR33s, I was
not yet stubborn enough to see value one way or the other (the links in
ROMs in my fingers were not yet programmed). By the time I left CMU and
the glass tty was all I was willing to use. I had become a UNIX/C person
more than anything else, so slashes as switches (and upper case and case
folding) had become annoying and just seemed wrong.
On Tue, Nov 28, 2017 at 8:19 AM, Noel Chiappa <jnc at mercury.lcs.mit.edu>
wrote:
> According to "The Evolution of the Unix Timesharing System", full path
> names
> arrived later than I/O redirection, so by they time they needed a
> separator,
> '>' and '<' were gone.
That was the impression I had had and I admit I think I must have either
assumed it, heard it in conversation, or maybe read it at some point in
this paper. Cann't say when I started to think same, but I came to UNIX
in Fifth and Sixth so, they were already there. I was just learning the
'UNIX way' at the time. I guess because I was using so many
different systems at the time, I was more willing to accept every dialect
had its way of doing things. As Greg points out EXEC-8 was hardly
anything like TSS/360 and learned them together. Same as TOPS/TWINEX and
eventually VMS.
Funny, things is I left those other systems and then was forced to come
back to them, first RT11 and then NOS/KRONOS and then VMS and I remember
grumbling. By then the ROMs had been forced in my muscle memory.
'/' also has the advantage of being a non-shift
>
> character!
>
Hmm, so was dot, which is what TSS and MTS used. DEC was using it as the
<base>.<ext> separator, but I think Ken could have used it as easily at the
time since the idea of <ext> and exposing semantics of what the file was in
the name was foreign to UNIX (although was used in other systems as we
know).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171128/9a5d41a4/attachment.html>
next prev parent reply other threads:[~2017-11-28 18:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 13:19 Noel Chiappa
2017-11-28 18:20 ` Clem Cole [this message]
2017-11-28 21:56 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2017-11-29 14:03 Noel Chiappa
2017-11-29 20:29 ` Charles Anthony
2017-11-29 1:23 Doug McIlroy
2017-11-29 1:37 ` George Michaelson
2017-11-29 2:22 ` Charles Anthony
[not found] <mailman.376.1511899437.9955.tuhs@minnie.tuhs.org>
2017-11-28 21:30 ` Paul Ruizendaal
2017-11-28 5:51 Jon Steinhart
2017-11-28 6:05 ` Dave Horsfall
2017-11-28 6:49 ` Andrew Warkentin
2017-11-28 11:18 ` Ralph Corderoy
2017-11-28 11:49 ` Michael Kjörling
2017-11-28 12:46 ` Ralph Corderoy
2017-11-28 18:01 ` Lawrence Stewart
2017-11-28 19:36 ` Paul Winalski
2017-11-28 20:03 ` Clem Cole
2017-11-28 6:28 ` Greg 'groggy' Lehey
2017-11-29 19:16 ` Steffen Nurpmeso
[not found] ` <20171204054651.GA17671@eureka.lemis.com>
[not found] ` <20171204215701.l9Pvr%steffen@sdaoden.eu>
2017-12-05 13:22 ` Steffen Nurpmeso
2017-12-07 5:15 ` Greg 'groggy' Lehey
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='CAC20D2MKRgpgiDaG6VtAM=qcuCPf89M-3fRfREQ=SAbC5+SAiw@mail.gmail.com' \
--to=clemc@ccc.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).