From: Steve Nickolas <usotsuki@buric.co>
To: "Michael Kjörling" <michael@kjorling.se>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] UNIX Backslash History
Date: Mon, 28 Oct 2019 11:08:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.02.1910281106290.77349@frieza.hoshinet.org> (raw)
In-Reply-To: <xzdtvssnnqfvfxq9swgv979g@localhost>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 815 bytes --]
On Mon, 28 Oct 2019, Michael Kjörling wrote:
> On 27 Oct 2019 21:11 -0400, from usotsuki@buric.co (Steve Nickolas):
>>
>> I can't imagine there's any such connection. MS-DOS got it from CP/M, which
>> didn't even have the concept of subdirectories until after MS-DOS did.
>
> If there was such a relationship, it would probably make more sense
> for the command prompt termination character to be ":", not ">", as
> DOS labelled devices as [whatever]: (like "A:" or "NUL:"). So I agree
> with Steve; I imagine it's unrelated. They just had to use _something_
> as a default to indicate that the computer is waiting for a command,
> and ">" is as good a character as any.
86-DOS actually did use ":" as a prompt character. This was changed for
IBM's release, for some clone releases, and for MS-DOS 2.0.
-uso.
next prev parent reply other threads:[~2019-10-28 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-27 20:31 Doug McIlroy
2019-10-27 20:42 ` Richard Salz
2019-10-27 20:49 ` Charles Anthony
2019-10-27 23:01 ` Grant Taylor via TUHS
2019-10-28 1:11 ` Steve Nickolas
2019-10-28 12:00 ` Michael Kjörling
2019-10-28 13:44 ` Clem Cole
2019-10-28 15:08 ` Steve Nickolas [this message]
2019-10-28 18:47 ` Dave Horsfall
2019-10-28 20:43 ` Paul Winalski
2019-10-27 20:46 ` Bakul Shah
2019-10-28 17:36 ` Anthony Martin
2019-10-28 18:17 ` Charles Anthony
-- strict thread matches above, loose matches on Subject: below --
2019-10-28 15:51 Noel Chiappa
2019-10-27 21:31 Noel Chiappa
2019-10-27 21:51 ` Charles Anthony
2019-10-26 9:39 Caipenghui
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=alpine.BSF.2.02.1910281106290.77349@frieza.hoshinet.org \
--to=usotsuki@buric.co \
--cc=michael@kjorling.se \
--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).