From: Scott Schwartz schwartz@finch.cse.psu.edu
Subject: [9fans] Questions
Date: Thu, 11 Sep 1997 17:32:13 -0400 [thread overview]
Message-ID: <19970911213213.XcR-YeYp9S9zgfjsF9m9sF9gQfnoLSgvLE0QIl0oGaQ@z> (raw)
David Hogan <dhog@lore.plan9.cs.su.oz.au> writes:
| Yes, but the suggestion which spawned this debate was that programs
| such as 8 1/2 which interpret the down arrow as the "view" key should
| interpret the arrow glyphs as control characters (after matching
| modifications to the console driver). As Rob points out, this is a
| bad idea since it makes it impossible for a user to insert literal
| arrow glyphs.
That's not entirely true, since you could always snarf one of those
reserved characters from a ½char window.
| Unicode defines certain characters which can be used as "control"
| characters. Attempting to use others this way would be a mistake.
But given that the architecture of the console device is to just
return characters, not events, you have to abuse some characters
or other. The "view" key is just the narrow end of the wedge.
Isn't it the case that there are OS reserved sections of the unicode
space that could be used for this sort of thing?
(Linux puts Klingon script there... do we want to buck the trend?)
| I actually like the way that all three of the bottom row of arrow
| keys act as the view key; one doesn't need to be so precise.
Hm. I have a hard time hitting the wrong arrow. Especially on a
keyboard with a t-bar configuration.
| Of course, you're free to redefine the keys in your own copy
| of the source!
It's much more fun to have some sort of consensus, rather than
a bunch of disparate hacks.
P.S. skull and crossbones is 2620.
next reply other threads:[~1997-09-11 21:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-11 21:32 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-21 4:32 [9fans] questions Skip Tavakkolian
1997-09-12 19:59 [9fans] Questions Pete
1997-09-11 20:15 David
1997-09-11 11:49 elliott
1997-09-11 9:29 Steve_Kilbane
1997-09-11 9:08 elliott
1997-09-10 18:17 rob
1997-09-10 18:09 Scott
1997-09-10 17:38 rob
1997-09-10 17:35 Scott
1997-09-10 13:46 Markus
1997-09-10 13:06
1997-09-03 9:42 Steve
1997-09-03 9:37 Steve
1997-09-02 17:22 Ed
1997-09-02 15:27 Nigel
1997-09-02 15:02 elliott
1997-09-02 13:25
1997-08-15 20:10 [9fans] questions
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=19970911213213.XcR-YeYp9S9zgfjsF9m9sF9gQfnoLSgvLE0QIl0oGaQ@z \
--to=9fans@9fans.net \
/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).