From: Andy Kosela <akosela@andykosela.com>
To: tuhs@tuhs.org, norman@oclsc.org
Subject: Re: [TUHS] cat -v and other complaints
Date: Fri, 07 Sep 2018 00:16:21 +0200 [thread overview]
Message-ID: <5b91a735.NY0ZEcIRVoU4KsK1%akosela@andykosela.com> (raw)
In-Reply-To: <1536265780.5213.for-standards-violators@oclsc.org>
Norman Wilson <norman@oclsc.org> wrote:
> Andy Kosela:
>
> One still cannot ignore the fact that Unix and Plan 9 offer two
> completely different approaches to displaying text.
>
> I admit I've never actually used Plan 9. Can you elaborate on
> the different approaches?
>
> One difference from most of what passes for UNIX these days is
> probably that the basic terminal model allows one to edit anything
> on the screen, using the mouse and keyboard and a simple button-2
> menu similar to that of sam. You can edit what some program has
> already printed, then pick it up and send it back as input. You
> can even edit text in the current line that hasn't been sent yet
> (because you haven't hit a return yet); in effect the canonical-line
> part of the tty driver is in the terminal.
>
> But you probably don't mean that, both because it's not really
> such a radical difference, and because it doesn't conflict at all
> with UNIX. In fact it originated on UNIX, five or six years before
> Plan 9 was thought of: it's the model from the terminal program
> in mux, the more-advanced version of the Blit/Jerq window manager
> that nearly everybody used in 1127 by the time I arrived in 1984.
>
> And I still use it every day, even on Linux (and in years past
> on Solaris and IRIX and Digital UNIX and Ultrix). The modern
> version of the program to do that is called 9term. It doesn't
> work quite as well as I'd like on Linux due to changes in the
> tty driver that make it hard for a program to learn right away
> when tty modes are changed (in particular when echo is turned off
> or on), and it does conflict with the GNU readline junk because
> that turns off canonical processing, but to those of us who have
> a taste for it it's still just fine.
>
> As I say, I don't think that's the difference you mean, so please
> step in and supersede me.
In short, character based approach vs. bitmap based. Yes, in Unix you
also has a windowing system which is bitmap based, but IMHO this was
always an add-on and not an essential part of the system. Plan 9 on the
other hand seems to be designed with more of a graphical based approach
than the old school character based approach.
--Andy
next prev parent reply other threads:[~2018-09-06 22:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 20:29 Norman Wilson
2018-09-06 22:16 ` Andy Kosela [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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 21:56 ` 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
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
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=5b91a735.NY0ZEcIRVoU4KsK1%akosela@andykosela.com \
--to=akosela@andykosela.com \
--cc=norman@oclsc.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).