The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Andy Kosela <akosela@andykosela.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] cat -v and other complaints
Date: Thu, 6 Sep 2018 21:59:05 -0400	[thread overview]
Message-ID: <CAEoi9W5BBxOsYvQ5RAiJWHy0CKRTxeUPOGFCDfs4zKkNvKmc6g@mail.gmail.com> (raw)
In-Reply-To: <5b91a268.lXqMJkXVvoGUv0XA%akosela@andykosela.com>

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

On Thu, Sep 6, 2018 at 5:56 PM Andy Kosela <akosela@andykosela.com> wrote:

> [snip]  Well, you can't tell me
> this system was designed with the idea of running it using text terminal
> and no mouse.


I won't, because it wouldn't be true. You are correct that it was always
intended to be used with a graphical console. But you keep talking about
"text terminals" and therein lies the confusion: our text terminals haven't
been purely "text" since the teletype days. Even green-screen serial
terminals have graphics adapters to draw characters on the screen.

There is also no cursor addressing, no curses.


Actually, there *is* a graphical program to emulate a vt-series terminal,
but pretty much no one uses it. So while strictly speaking this is
incorrect, it is essentially correct for all intents and purposes.

But it begs the question: why would you *want* to use that sort of
interface? That was appropriate for an HP or DEC terminal connected via a
low-bandwidth link (e.g., serial) or a shared host computer. Once we moved
onto personal workstation-class machines with graphics adapters, why
continue with that paradigm? Your framebuffer doesn't care that,
'\033[H\033[J' means "move the cursor to the upper-left corner and clear
the current line to the end of the screen", so why should your terminal
emulator? For that matter, if logged into the text-only console on a Linux
or FreeBSD machine, why does running `stty` say your graphics adapter has a
BAUD rate? The plan9 authors decided to leave such historical debris behind.


> Like I
> written before it was born in the different era -- they tried to not
> build it on the idea of character based TTY, but rather incorporate
> graphical element into it.
>

Correct. I wasn't there, but the observation surely must have been in part
that the user was *already* using a graphical environment, just not to very
good effect.

If it is possible to be fully productive in Plan 9 using just VGA text
> mode (720x400) and not any of the bitmap modes, with Unix like cursor
> addressing and with no rio(1) and no mouse then it's something I never
> really explored.
>

You could skip `rio` and just run `vt` on the console. I doubt the
emulation is very good and it wouldn't be an acceptable substitute for
serious use. `vt` was really intended as a stop-gap for accessing older
systems; the plan9 model was different, and instead of accessing remote
resources, the idea was that those resources would be shared with the
(plan9) network and imported locally for manipulation. That is, I wouldn't
`ssh` into some machine to make use of something on it; instead I'd use
`import` to bring those resources into my namespace locally and I'd
manipulate them there.

I did a writeup of this a while back:
http://pub.gajendra.net/2016/05/plan9part1

I should probably do parts 2 and 3....

        - Dan C.

[-- Attachment #2: Type: text/html, Size: 3955 bytes --]

  reply	other threads:[~2018-09-07  2:00 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 14:25 Clem Cole
2018-08-29 22:34 ` Dave Horsfall
2018-08-29 23:36   ` Larry McVoy
2018-08-30  1:14     ` Clem cole
2018-08-30  1:15       ` Clem cole
2018-08-30  2:43       ` Kevin Bowling
2018-08-30  2:59         ` George Michaelson
2018-08-31  0:27         ` Dave Horsfall
2018-08-31  0:41           ` Dan Cross
2018-08-31  1:58             ` Larry McVoy
2018-08-31 11:38           ` ron
2018-08-31 14:41           ` [TUHS] UNIX System names - since UNIX was a Trademark Clem Cole
2018-08-31 15:13             ` Eric Wayte
2018-08-31 15:17             ` William Pechter
2018-08-31 15:25               ` Clem Cole
2018-09-01  0:10               ` John P. Linderman
2018-09-01  0:18                 ` ron
2018-09-01  0:55                   ` Nemo
2018-09-01  7:37                     ` Dave Horsfall
2018-09-01 13:54                       ` Nemo
2018-09-01 17:03                       ` Paul Winalski
2018-09-03  1:14                         ` Robert Brockway
2018-09-30 20:57                 ` Lyndon Nerenberg
2018-10-01 16:26                   ` Paul Winalski
2018-09-01  0:00             ` Dave Horsfall
2018-08-31 21:56 ` [TUHS] cat -v and other complaints Cág
2018-09-01  3:37   ` Andrew Warkentin
2018-09-03 18:04     ` Cág
2018-09-03 18:11       ` Kurt H Maier
2018-09-03 18:56         ` Cág
2018-09-04  6:10           ` Andy Kosela
2018-09-04  6:41             ` ron minnich
2018-09-04  9:34               ` Andy Kosela
2018-09-04 10:23                 ` Dan Cross
2018-09-04 14:22                 ` ron minnich
2018-09-06 20:02                   ` Andy Kosela
2018-09-06 20:49                     ` ron minnich
2018-09-06 21:55                       ` Andy Kosela
2018-09-07  1:59                         ` Dan Cross [this message]
2018-09-07  4:40                           ` Andy Kosela
2018-09-30 21:32           ` Lyndon Nerenberg
2018-09-03 20:08         ` Bakul Shah
2018-09-03 20:41           ` Kurt H Maier
2018-09-03 21:46             ` Bakul Shah
2018-09-04  0:52               ` Kurt H Maier
2018-09-06 20:29 Norman Wilson
2018-09-06 22:16 ` Andy Kosela
2018-09-08 12:02 [TUHS] [TUHS} " Doug McIlroy
2018-09-08 13:36 ` Will Senn
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=CAEoi9W5BBxOsYvQ5RAiJWHy0CKRTxeUPOGFCDfs4zKkNvKmc6g@mail.gmail.com \
    --to=crossd@gmail.com \
    --cc=akosela@andykosela.com \
    --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).