The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Where did the "~" come from
Date: Thu, 19 Nov 2020 09:41:29 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.2011190931000.48674@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2N56ZE=gizt_wu_ujUn3B4_O=UgGH-HNBNgiCc_-9YTCg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

On Wed, 18 Nov 2020, Clem Cole wrote:

> In our exchange, someone observed suggested that Joy might have picked 
> it up because the HOME key was part of the tilde key on the ADM3A, which 
> were popular at UCB [i.e. the reason hjkl are the movement keys on vi is 
> the were embossed on the top of those keys on the ADM3A].  It also was 
> noted that the ASR-33 lacks a ~ key on its keyboard.  But Lesk 
> definitely needed something to represent a remote user's home directory 
> because each system was different, so he was forced to use something.

The ADM-3A was one of the best terminals ever made.

> It was also noted that there was plenty of cross-pollination going on as
> students and researchers moved from site to site, so it could have been BTL
> to UCB, vice-versa, or some other path altogether.
> 
> So two questions for this august body are:
>  1. Where did the ~ as $HOME convention come to UNIX?

Gawd...  I think I saw it in PWB, but I'm likely wrong.

>  2. Did UNIX create the idiom, or was there an earlier system such as CTSS,
>     TENEX, ITS, MTS, TSS, or the like supported it?

No idea. but given that Unix inherited a lot of stuff....

-- Dave

  reply	other threads:[~2020-11-18 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-18 22:25 Clem Cole
2020-11-18 22:41 ` Dave Horsfall [this message]
2020-11-19  0:44   ` George Michaelson
2020-11-19 13:45     ` Ron Natalie
2020-11-19 16:16     ` Chet Ramey
2020-11-19 15:50 ` Warner Losh
2020-11-19 17:22 ` Mary Ann Horton
2020-11-19 18:43   ` Clem Cole
2020-11-19 20:02     ` Michael Kjörling

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.21.9999.2011190931000.48674@aneurin.horsfall.org \
    --to=dave@horsfall.org \
    --cc=tuhs@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).