The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Slashes (was: MS-DOS)
Date: Fri, 8 Jul 2016 17:06:12 +1000	[thread overview]
Message-ID: <20160708070612.GG78278@eureka.lemis.com> (raw)
In-Reply-To: <7c94ef6c9ee764ea94e3e79794c663d9.squirrel@webmail.yaccman.com>

On Thursday,  7 July 2016 at 22:40:47 -0700, scj at yaccman.com wrote:
>
>>
>>>> I would argue "solidus" is closer.
>>>
>>> SOLIDUS is the Unicode name, too, as is REVERSE SOLIDUS, giving
>>> SLASH and BACKSLASH as secondaries.
>>
>> Finally we have clarity!  From now on it's only (without shouting)
>> solidus and reverse solidus.  No confusion any more, at least not for
>> those in the know.
>
> What fun!  Having disposed of # and / and \, anybody want to find
> other obscure names for the other operators?  Soon we could be as
> obscure as Algol 68!

That takes real talent.

You've made me locate my Report (not Revised Report).  It's
surprisingly dog-eared.  I'll go through it and see what I can find,
but for the moment section 2.2 seems appropriate.

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160708/206a81aa/attachment.sig>


  reply	other threads:[~2016-07-08  7:06 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02  0:12 [TUHS] MS-DOS Norman Wilson
2016-07-02  1:13 ` Steve Nickolas
2016-07-02  4:52   ` Random832
2016-07-03 19:40   ` scj
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 [this message]
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
2016-07-08 11:25 Norman Wilson
2016-07-08 13:16 ` John Cowan
2016-07-08 14:06   ` Brantley Coile
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
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-08 17:36 Norman Wilson
2016-07-10  1:41 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

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=20160708070612.GG78278@eureka.lemis.com \
    --to=grog@lemis.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).