unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Walters <walters@debian.org>
Subject: Re: German tutorial fix
Date: 20 May 2002 17:13:33 -0400	[thread overview]
Message-ID: <1021929213.29245.3300.camel@space-ghost> (raw)
In-Reply-To: <87bsbaj318.fsf@lexx.delysid.org>

On Mon, 2002-05-20 at 10:40, Mario Lang wrote:

> Uhm, thats nice. So it's impossible for me to work well. Nice, good that
> I now know this.
> 
> Please stop this thread, it's extremely pointless. I, for my part, use
> cursor keys.  I use a laptop sized keyboard, so I really don't need
> to move my hands that far.  And everytime I try to use C-f C-b C-n C-p
> it feels like it's much more strain for my left hand. On the other hand,
> M-f and M-b and alike are really useful, as they move more than one
> char. But having to hit two keys to achieve one movement
> feels just wrong to me.  So I think we can conclude that
> there are different viewpoints, and that there is no single best
> solution.

Well said.  I personally use VIPER, but when I'm in a mode which is in
Emacs state, I much prefer using the arrow keys over C-f and friends.

  reply	other threads:[~2002-05-20 21:13 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14 13:07 German tutorial fix Mario Lang
2002-05-14 15:05 ` Kai Großjohann
2002-05-16  7:22   ` Richard Stallman
2002-05-16 10:37     ` Kai Großjohann
2002-05-16 12:52       ` Eli Zaretskii
2002-05-16 14:10         ` Andreas Fuchs
2002-05-16 15:37           ` Eli Zaretskii
2002-05-17 19:28         ` Richard Stallman
2002-05-18  0:44           ` Francesco Potorti`
2002-05-18  2:00             ` Miles Bader
2002-05-18  7:17               ` Andreas Fuchs
2002-05-18 11:59               ` Francesco Potorti`
2002-05-18 12:12                 ` Miles Bader
2002-05-18 12:55                   ` Eli Zaretskii
2002-05-18 13:11                     ` Andreas Fuchs
2002-05-19  4:56                       ` Eli Zaretskii
2002-05-19  5:30                       ` Richard Stallman
2002-05-18 20:36                     ` Kim F. Storm
2002-05-20 22:58                   ` Francesco Potorti`
2002-05-19  5:30                 ` Richard Stallman
2002-05-19 12:54                   ` Alex Schroeder
2002-05-19 13:30                     ` Miles Bader
2002-05-19 14:47                       ` Stefan Monnier
2002-05-19 15:26                       ` Alex Schroeder
2002-05-19 16:10                         ` Miles Bader
2002-05-20 10:47                           ` Alex Schroeder
2002-05-23 19:45                         ` Robert J. Chassell
2002-05-23 23:45                           ` Alex Schroeder
2002-05-20 14:48                       ` Richard Stallman
2002-05-18 14:18               ` Alex Schroeder
2002-05-18  6:44             ` Eli Zaretskii
2002-05-19 19:44             ` Robert J. Chassell
2002-05-20 14:40               ` Mario Lang
2002-05-20 21:13                 ` Colin Walters [this message]
2002-05-17 19:28       ` Richard Stallman
2002-05-15  0:13 ` Werner LEMBERG
2002-05-15  4:41   ` Eli Zaretskii

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=1021929213.29245.3300.camel@space-ghost \
    --to=walters@debian.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).