From: elliott Elliott.Hughes@genedata.com
Subject: [9fans] Questions
Date: Thu, 11 Sep 1997 11:08:12 +0200 [thread overview]
Message-ID: <19970911090812.NnYUxS6J5zeOQL4GWGqxV7pZHJtFpK0zknOadM3JTTk@z> (raw)
rob@plan9.bell-labs.com wrote:
>
> > In these internationalized days, shouldn't the arrows send unicode
> > arrow chars?
>
> Certainly not. The arrow keys are control characters; the arrow
> characters are printable glyphs. This is like suggesting CR print
> as a little down-and-to-the-left arrow.
That's nonsense. The keys are what we choose to interpret them as. The
"Return" key is a control key because that's the convention. The key
with "W" painted on it is not because that's the convention.
As I see it, if the arrow keys aren't going to be used as distinct
control keys then it makes perfect sense to have them output Unicode
arrow characters. It might not be terribly useful, but we could use <-
for assignment and -> to separate guards from commands, for example.
Which is a lot more sensible than sending 16_80.
--
Elliott Hughes - GeneData AG, Postfach 254, CH-4016 Basel, Switzerland
mailto:elliott.hughes@genedata.com http://users.ch.genedata.com/~enh/
next reply other threads:[~1997-09-11 9:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-11 9:08 elliott [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 21:32 Scott
1997-09-11 20:15 David
1997-09-11 11:49 elliott
1997-09-11 9:29 Steve_Kilbane
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=19970911090812.NnYUxS6J5zeOQL4GWGqxV7pZHJtFpK0zknOadM3JTTk@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).