From: Sven Utcke <utcke+news@informatik.uni-hamburg.de>
Subject: Re: C-f, C-b, C-n and C-p or right, left, down, up?
Date: 06 Oct 2003 16:23:24 +0200 [thread overview]
Message-ID: <vd0pthatpgj.fsf@kogs31.informatik.uni-hamburg.de> (raw)
In-Reply-To: mailman.1038.1065134760.21628.help-gnu-emacs@gnu.org
Joe Corneli <jcorneli@math.utexas.edu> writes:
> Don't type like a monkey.
>
> Mode_switch u -- Right
> Mode_switch o -- Left
> Mode_switch e -- Down
> Mode_switch . -- Up
>
> The QWERTY equivalent would be semiacceptable, but you'd still be left
> with the residual psychic confusion brought about by mixing vowels and
> consonants. Never mix, never worry!
Aeh, that's for a Dvorak keyboard? What would this be on QWERTY?
Sven
--
_ __ The Cognitive Systems Group
| |/ /___ __ _ ___ University of Hamburg
| ' </ _ \/ _` (_-< phone: +49 (0)40 42883-2576 Vogt-Koelln-Strasse 30
|_|\_\___/\__, /__/ fax : +49 (0)40 42883-2572 D-22527 Hamburg
|___/ http://kogs-www.informatik.uni-hamburg.de/~utcke/home.html
next prev parent reply other threads:[~2003-10-06 14:23 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1A4kP0-00064x-AV@monty-python.gnu.org>
2003-10-02 22:45 ` C-f, C-b, C-n and C-p or right, left, down, up? Joe Corneli
[not found] ` <mailman.1038.1065134760.21628.help-gnu-emacs@gnu.org>
2003-10-06 14:23 ` Sven Utcke [this message]
2003-10-16 22:32 Joe Corneli
-- strict thread matches above, loose matches on Subject: below --
2003-10-01 8:03 Barman Brakjoller
2003-10-01 8:43 ` Noufal Ibrahim
2003-10-01 10:16 ` David Kastrup
2003-10-01 17:02 ` Daniel B.
[not found] ` <mailman.949.1065027827.21628.help-gnu-emacs@gnu.org>
2003-10-01 17:39 ` David Kastrup
2003-10-02 16:16 ` Hans-Christoph Wirth
2003-10-07 18:33 ` David Steuber
2003-10-03 10:31 ` Daniel B.
2003-10-08 23:52 ` Jim Janney
2003-10-09 18:50 ` Barry Margolin
2003-10-16 21:07 ` Kai Grossjohann
2003-10-07 18:29 ` David Steuber
2003-10-09 17:11 ` Daniel B.
[not found] ` <mailman.1425.1065719518.21628.help-gnu-emacs@gnu.org>
2003-10-09 19:42 ` David Steuber
2003-11-03 2:34 ` David Combs
2003-10-01 12:00 ` Arjan Bos
2003-10-01 15:48 ` Barry Margolin
2003-10-02 14:21 ` Arjan Bos
2003-10-06 17:30 ` Gareth Rees
2003-10-01 12:34 ` Stefan Monnier
2003-10-01 12:48 ` Jay Belanger
2003-10-07 18:40 ` David Steuber
2003-10-07 20:02 ` Stefan Monnier
2003-10-07 21:11 ` David Kastrup
2003-10-08 8:48 ` Oliver Scholz
2003-10-08 10:21 ` Eli Zaretskii
[not found] ` <mailman.1313.1065608391.21628.help-gnu-emacs@gnu.org>
2003-10-08 10:27 ` David Kastrup
2003-10-08 15:47 ` Barry Margolin
2003-10-09 20:39 ` lawrence mitchell
2003-10-09 18:15 ` Daniel B.
2003-10-01 12:36 ` Jim Ottaway
2003-10-01 15:07 ` Kevin Rodgers
2003-10-01 16:43 ` Daniel B.
2003-10-02 13:59 ` Arthur Davis
[not found] ` <mailman.985.1065065051.21628.help-gnu-emacs@gnu.org>
2003-10-02 8:40 ` Matthias Meulien
2003-10-03 10:31 ` Daniel B.
[not found] ` <mailman.1056.1065177296.21628.help-gnu-emacs@gnu.org>
2003-10-16 21:03 ` Kai Grossjohann
2003-10-16 21:13 ` lawrence mitchell
2003-10-06 14:21 ` Sven Utcke
2003-10-06 15:35 ` Barry Margolin
2003-10-07 16:29 ` Hans-Christoph Wirth
2003-10-07 21:11 ` David Kastrup
2003-10-09 15:17 ` Per Abrahamsen
2003-10-09 17:08 ` Daniel B.
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vd0pthatpgj.fsf@kogs31.informatik.uni-hamburg.de \
--to=utcke+news@informatik.uni-hamburg.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).