From: John Mastro <john.b.mastro@gmail.com>
To: "help-gnu-emacs@gnu.org" <Help-gnu-emacs@gnu.org>
Cc: Robert Thorpe <rt@robertthorpeconsulting.com>
Subject: Re: Find bindings for all modes
Date: Wed, 29 Oct 2014 16:05:14 -0700 [thread overview]
Message-ID: <CAOj2CQQ=rH=TiVEXz4GdF-+XuvnXXU1_Ox07HjgYzkq7ah42Mg@mail.gmail.com> (raw)
In-Reply-To: <87a94fince.fsf@robertthorpeconsulting.com>
Robert Thorpe <rt@robertthorpeconsulting.com> wrote:
> I'm not sure I understand John Mastro & Tim Johnson are trying to
> achieve here. However, there are a few keys that are much less trouble
> to use:
Fair warning - this will probably be of interest to approximately noone,
but I'll share my thinking anyway :)
My goal is to have a general-purpose prefix key on the right hand side
of the keyboard, to complement C-c.
> * C-' C-# C-. C-, C-; C-=.
> Undefined by default.
Besides the problem with terminals, there's a sense in which unbound
keys are less attractive for my purpose than using C-h. Keys that are
unbound by default are an understandably attractive option for mode
authors. On the other hand, no mode that I know of rebinds C-h, so I
only deal with the issue once. Also, these are all either pinky keys,
off the home row, or both.
> * C--, C-1, C-2,..., M--, M-1, M-2, ....
> These are duplicates. If you like you can use one set of them and
> redefine the other. Notice that C-4 & M-4 are almost useless since
> in most circumstances they do the same thing as C-u.
I like having numeric args on both control and meta. I can see the case
for {C,M}-4 (although there are counter-examples) but I find the idea of
treating 4 differently a bit ugly. Also, they're off the home row.
> * M-o.
> This isn't very useful unless you use enriched-mode.
Indeed, I use M-o for `ace-window' (an `other-window' replacement).
> * M-s.
> The existing M-s prefix key doesn't have very much in it. Eventually the
> Emacs maintainers will put more in no-doubt, but until then you can put
> a few things in it.
This is on the left hand side of the keyboard, whereas I want something
on the right. As you point out, we already have C-c on the left.
> * C-c X.
> This is left as the default user-defined prefix key.
I use this a lot and am happy with it for many things, though not all. I
want a prefix key on the right to complement C-c, not to replace it.
> Some of these don't work in terminals, I don't know which ones because I
> don't use terminals.
I do use terminals regularly, but I still haven't managed to memorize
all the differences and at least once a week I manage to surprise myself
when something doesn't work.
--
john
next prev parent reply other threads:[~2014-10-29 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 17:58 Find bindings for all modes Tim Johnson
2014-10-28 21:53 ` John Mastro
2014-10-28 22:00 ` Tim Johnson
2014-10-28 22:18 ` John Mastro
2014-10-29 0:31 ` Tim Johnson
2014-10-29 3:09 ` Robert Thorpe
2014-10-29 18:19 ` Tim Johnson
2014-10-29 23:05 ` John Mastro [this message]
2014-10-30 1:46 ` Tim Johnson
2014-10-30 2:04 ` Robert Thorpe
2014-10-30 18:25 ` Tim Johnson
2014-11-01 21:00 ` Robert Thorpe
2014-11-04 0:04 ` Tim Johnson
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='CAOj2CQQ=rH=TiVEXz4GdF-+XuvnXXU1_Ox07HjgYzkq7ah42Mg@mail.gmail.com' \
--to=john.b.mastro@gmail.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=rt@robertthorpeconsulting.com \
/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).