From mboxrd@z Thu Jan  1 00:00:00 1970
From: paul.winalski@gmail.com (Paul Winalski)
Date: Tue, 28 Nov 2017 14:36:21 -0500
Subject: [TUHS] Dash options
In-Reply-To: <CAD-qYGpTk9PhTMQcmtuZqpPkSSUGvQO4bDrjSnUYegqdjy7Jug@mail.gmail.com>
References: <201711280551.vAS5pDZt014974@darkstar.fourwinds.com>
 <alpine.BSF.2.21.1711281703290.780@aneurin.horsfall.org>
 <CAD-qYGpTk9PhTMQcmtuZqpPkSSUGvQO4bDrjSnUYegqdjy7Jug@mail.gmail.com>
Message-ID: <CABH=_VRE2BG7rpduCPxECBc7m4dFwyvcG3gm25ZwTrN8VpkA-A@mail.gmail.com>

On 11/28/17, Andrew Warkentin <andreww591 at gmail.com> wrote:
>
> Multics had dash options, so that's presumably where Unix got them
> from. I believe slash options were mostly a DEC thing that DOS and its
> successors borrowed (I think they originated in TOPS-10).

That's how I remember it.  I think slash was chosen because it looks
somewhat like a toggle switch.  MS/DOS patterned its command line
syntax after RT-11 and inherited the slash as a command option
introduction from there.  Unfortunately this meant that they couldn't
use slash as a directory separator when they got a hierarchical file
system, and so they chose backslash instead.  Nowadays the Windows
shell, and I think also the underlying image activation system
service, use an ugly algorithmic hack to support both directions of
slashes in file pathnames.

-Paul W.