The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] [TUHS} cat -v and other complaints
Date: Sat, 8 Sep 2018 08:36:56 -0500	[thread overview]
Message-ID: <3054F86A-0FDA-4266-B8B8-EE53869F3700@gmail.com> (raw)
In-Reply-To: <201809081202.w88C2OCj038136@tahoe.cs.Dartmouth.EDU>

Doug et al.,

I’m interested in learning about this curses vs blit business. Is there a writeup or book chapter out there that covers this in any detail?

Thanks,

Will

Sent from my iPhone

On Sep 8, 2018, at 7:02 AM, Doug McIlroy <doug@cs.dartmouth.edu> wrote:

>> you can't tell me
>> this system was designed with the idea of running it using text terminal
>> and no mouse.  There is also no cursor addressing, no curses.
> 
> The well named Curses and the associated vi were an ugly outgrowth
> of glass screens--an outgrowth many of us in the Unix lab never
> adopted. That branch of evolution was unrelated to the Blit branch that
> essentially preserved the old TTY interface, except that one could have
> multiple terminals on screen and a mouse was available to give mechanical
> help for manual cut/paste/edit activities. Plan 9 terminal-handling
> smoothly continued that evolutionary branch.
> 
> Mouse support could have been used to take off in a radical direction,
> but it wasn't. To my mind, the primary innovation in Plan 9 was not
> terminal support, nor everything-is-a-file. Rather it was an advance in
> what Vyssotsky called "distributable computing", where components can
> collaborate in a uniform way, no matter where they are. The key was the 9P
> protocol that unpacked the notion of file type--a unifying principle
> that brought simplicity and generality to a diversity of particulars.

  reply	other threads:[~2018-09-08 13:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-08 12:02 Doug McIlroy
2018-09-08 13:36 ` Will Senn [this message]
2018-09-08 14:22   ` [TUHS] " Ralph Corderoy
2018-09-08 16:10     ` Arthur Krewat

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=3054F86A-0FDA-4266-B8B8-EE53869F3700@gmail.com \
    --to=will.senn@gmail.com \
    --cc=doug@cs.dartmouth.edu \
    --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).