9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Derek Peschel <dpeschel@eskimo.com>
To: 9fans@cse.psu.edu
Subject: [9fans] terminal types and photos?
Date: Mon, 15 Mar 2004 10:43:23 +0000	[thread overview]
Message-ID: <6b26c83b.0403131930.7afe96e1@posting.google.com> (raw)

 From keyboard(6) and "The Various Ports" I came up with this list of terminals
that Plan 9 has supported:

Carerra
Gnot
PC
Alpha PC
Viaduct
NeXT
SLC (is that a Sun?)
SparcStation 2
Magnum

Is that all?  Does anyone have photos of the custom ones?  If you combined
all the features that Plan 9 programs expect from the keyboard, what would
the result look like and what would it send to the computer?

Personally, I think a keyboard should simply send up/down messages and let
the computer do the decoding.  It should also have enough modifier keys
to allow at least 256 characters to be sent.  When it's appropriate, programs
should accept key sequences rather than ASCII characters since Control-Shift-A
may be useful.  I'm not advocating Emacs or anything like it (it's based on
constant hacking rather than planning) but I don't want to give up keyboard-
controlled programs, or the right to use any sequences I can type.  I'm also
not saying every command or character should be typable in one stroke.

I know many 9fans prefer mice.  I would need a mouse pointer I can see,
and a set of mouse gestures that allows me to work with structured data,
before I could change.  I do think mice win when you are doing work that may
involve any part of the screen.

-- Derek


             reply	other threads:[~2004-03-15 10:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 10:43 Derek Peschel [this message]
2004-03-15 11:18 ` Geoff Collyer
2004-03-15 11:29   ` Geoff Collyer
2004-03-15 11:34     ` a
2004-03-15 12:07       ` Geoff Collyer
2004-03-15 11:31   ` Charles Forsyth
2004-03-15 11:37     ` Geoff Collyer
2004-03-15 11:52       ` Charles Forsyth
2004-03-15 17:40   ` Derek Peschel
2004-03-16  2:17 ` rog
2004-03-15 15:45 Richard C Bilson

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=6b26c83b.0403131930.7afe96e1@posting.google.com \
    --to=dpeschel@eskimo.com \
    --cc=9fans@cse.psu.edu \
    /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).