From: David.Kastrup@t-online.de (David Kastrup)
Cc: Juanma Barranquero <jmbarranquero@laley.wke.es>
Subject: Re: Idea for compilation mode
Date: 08 Jun 2003 04:38:59 +0200 [thread overview]
Message-ID: <x53cilqon0.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E19Oog9-0004am-Ry@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> I'm not interested in making any major changes in Emacs key bindings
> for the sake of non-US keyboards. It would be too much trouble.
Naturally. It is just a thing to keep in mind for creating keymaps
that some keys are often worse to reach than others, when switching to
a different language. ` is an example for a key that is horrible to
type on almost any keyboard except US ones, and so it should be
avoided for important key bindings like next-error.
> However, it might perhaps make sense to support optional alternate
> binding themes for some of these layouts. Those could be maintained
> by users of those keyboard layouts, perhaps using
> key-translation-map to make them independent of the rest of Emacs.
> That way, they won't be a maintenance burden.
That would be overkill, I guess. Most keybindings for Emacs are
designed not for ergonomicity, but for their mnemonic value. For
example, C-b C-f C-p C-n make just as little sense on a Dvorak
keyboard as they do on an American. This is in stark difference to
the bindings of vi, where the cursor movements hjkl very much depend
on a Qwert-based keyboard layout in order to work.
In my opinion, national keyboard themes would not be worth the trouble
for Emacs, but keeping in mind keys like "`@\" and a few others as
being awkward in particular in connection with modifier keys will be a
boon for many users.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-06-08 2:38 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 22:41 Idea for compilation mode Richard Stallman
2003-06-03 7:42 ` Stephan Stahl
2003-06-03 8:01 ` David Kastrup
2003-06-03 10:20 ` Miles Bader
2003-06-03 16:14 ` Kevin Rodgers
2003-06-03 12:11 ` Frank Schmitt
2003-06-03 11:24 ` Kai Großjohann
2003-06-03 13:14 ` Stephan Stahl
2003-06-03 13:42 ` Kai Großjohann
2003-06-03 14:08 ` Stephan Stahl
2003-06-03 14:16 ` Stefan Monnier
2003-06-05 0:07 ` Richard Stallman
2003-06-05 0:07 ` Richard Stallman
2003-06-04 8:53 ` Richard Stallman
2003-06-04 9:37 ` Miles Bader
2003-06-04 10:23 ` David Kastrup
2003-06-04 10:27 ` Stephan Stahl
2003-06-04 15:19 ` Andreas Schwab
2003-06-05 6:25 ` Stephan Stahl
2003-06-05 13:07 ` Andreas Schwab
2003-06-05 13:31 ` Stephan Stahl
2003-06-05 13:37 ` Stefan Monnier
2003-06-05 14:00 ` Lute Kamstra
2003-06-05 23:02 ` Miles Bader
2003-06-05 23:08 ` Stefan Monnier
2003-06-07 12:01 ` Kai Großjohann
2003-06-05 10:57 ` Richard Stallman
2003-06-06 1:45 ` Miles Bader
2003-06-06 6:11 ` David Kastrup
2003-06-06 8:58 ` Stephan Stahl
2003-06-06 9:49 ` David Kastrup
2003-06-06 12:01 ` Stephan Stahl
2003-06-06 12:41 ` Juanma Barranquero
2003-06-06 13:40 ` Stephan Stahl
2003-06-06 17:55 ` Juanma Barranquero
2003-06-11 8:22 ` Stephan Stahl
2003-06-06 21:35 ` Frank Schmitt
2003-06-08 1:09 ` Richard Stallman
2003-06-08 2:38 ` David Kastrup [this message]
2003-06-09 17:12 ` Juanma Barranquero
2003-06-11 8:36 ` Stephan Stahl
2003-06-11 8:51 ` David Kastrup
2003-06-12 7:42 ` Juanma Barranquero
2003-06-06 15:40 ` David Kastrup
2003-06-06 16:49 ` Stephan Stahl
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=x53cilqon0.fsf@lola.goethe.zz \
--to=david.kastrup@t-online.de \
--cc=dak@gnu.org \
--cc=jmbarranquero@laley.wke.es \
/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).