From: David.Kastrup@t-online.de (David Kastrup)
Cc: Miles Bader <miles@gnu.org>
Subject: Re: Idea for compilation mode
Date: 06 Jun 2003 11:49:37 +0200 [thread overview]
Message-ID: <x5d6hr1qoe.fsf@lola.goethe.zz> (raw)
In-Reply-To: <1054889927.3ee057c7688fe@webmail.isogmbh.de>
Stephan Stahl <stl@isogmbh.de> writes:
> Miles Bader <miles@lsi.nec.co.jp> wrote:
>
> > There seems to be something of a consensus developing in this
> > thread for using `C-x C-n' and `C-x C-p' for next/previous-error,
> > moving mark-page to `C-x p', and simply removing the default
> > binding for set-goal-column.
>
> If set-goal-column should be on a key maybe C-x , can be used. Thats
> not far away from the old C-x C-n and C-x . which is directly beside
> would be somehow similar in function (set-fill-prefix). I think we
> should stop soon or we'll end up remapping all keys :-).
Which would not be the worst thing. As I said, it would be a viable
task for the TODO list to go through the existing, historically grown
keymappings with a fine comb, try to compare the probable usefulness
of mappings with their mnemonic characteristics and their awkwardness
(taking non-American keyboard layouts somewhat into mind as well) or
non-existence, and try to develop something better suited for
accessing the currently available functionality.
Language reform processes suffer a similar combination of growing
necessity, getting rid of obsolescent features that have fallen into
disuse, resistance from people accustomed to the old bindings, polling
people for what they commonly use for circumventing perceived
shortcomings and so on.
As I said, TODO list material. A good task, but needing considerable
effort if done right and thoroughly.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2003-06-06 9:49 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5d6hr1qoe.fsf@lola.goethe.zz \
--to=david.kastrup@t-online.de \
--cc=dak@gnu.org \
--cc=miles@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.