9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jpc@rpi.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dvorak
Date: Tue, 23 Dec 2003 10:15:23 -0500	[thread overview]
Message-ID: <53dcfefc5c5296d967848caf6ffee6c2@rpi.edu> (raw)
In-Reply-To: <3FE78190.5040101@ajft.org>

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

i've always thought a great keyboard would have lcd's on each key
rather than a printed letter.  switch from dvorak to qwerty to
whatever at a command and the keyboard still reads correctly.  you
could show which greek letter or funny math symbol a key would
generate when appropriate (alt, shift, special mode of software or
whatever)

john

[-- Attachment #2: Type: message/rfc822, Size: 4445 bytes --]

From: Adrian Tritschler <ajft@ajft.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] dvorak
Date: Tue, 23 Dec 2003 10:43:12 +1100
Message-ID: <3FE78190.5040101@ajft.org>

Brantley Coile wrote:
>>it's also much fun to set the system back to qwerty and have the
>>keycaps bear no relationship to what shows up on the screen...
> 
> 
> I helped a friend debug a program that worked while he was sitting
> down, but didn't while he was standing up.  We spend about 30 minutes
> puzzing over this until I noticed that someone has swapped two
> of his key caps.  While he was sitting he touch typed and while
> he was standing he was hunting and pecking, and hitting the
> incorrect key.

Ouch! sneaky.

I found myself stuck in a foreign internet cafe once, unable to login to 
my web-based email system.  I had no idea what my password was, I knew 
what the finger pattern was to type the password - but only on a QWERTY 
keyboard.

Whichever one you're used to, finding yourself at a different keyboard 
is a major irritation, especially in a foreign place while paying $10 
per hour to try and read email on a badly maintained filthy windows 98 
PC, connected by a piece of wet string to the internet.

> I don't think we were the first to have this mysterious bug.
> 
>  Brantley

---------------------------------------------------------------
Adrian Tritschler                          mailto:ajft@ajft.org
Latitude 38°S, Longitude 145°E, Altitude 50m,      Shoe size 44
---------------------------------------------------------------

  parent reply	other threads:[~2003-12-23 15:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-21 13:46 [9fans] simple keyboard question Hugo Santos
2003-12-21 17:07 ` Rob Pike
2003-12-21 21:00   ` [9fans] dvorak Michael Baldwin
2003-12-22  9:48     ` a
2003-12-22 14:21       ` Brantley Coile
2003-12-22 23:43         ` Adrian Tritschler
2003-12-23  6:38           ` boyd, rounin
2003-12-23 15:15           ` jpc [this message]
2003-12-23 16:28             ` Rob Pike
2003-12-23 20:07               ` Joel Salomon
2003-12-23 20:40                 ` Richard Miller
2003-12-23 23:53           ` Steve Kilbane
2003-12-21 21:14   ` [9fans] simple keyboard question Rasputin
2003-12-22  7:20   ` boyd, rounin
2003-12-21 22:14 ` Hugo Santos
2003-12-22  8:43   ` Fco.J.Ballesteros
  -- strict thread matches above, loose matches on Subject: below --
2000-06-19 15:04 [9fans] Dvorak presotto
2000-06-18 21:07 Hiroki Tamakoshi
2000-06-18 20:10 James A. Robinson

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=53dcfefc5c5296d967848caf6ffee6c2@rpi.edu \
    --to=jpc@rpi.edu \
    --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).