From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode + icicles, avoid key binding redefinitions?
Date: Wed, 29 Jan 2014 08:16:39 -0500 [thread overview]
Message-ID: <87k3dj6i88.fsf@gmail.com> (raw)
In-Reply-To: 52E8E982.6070701@miszellen.de
Florian Beck <fb@miszellen.de> writes:
> On 28.01.2014 10:08, Bastien wrote:
>
>> I think most of these keybindings could migrate to a C-c C- version.
>
> There is no need for migrating them IMO.
>
> The recommendation is:
>
> Sequences consisting of `C-c' followed by any other punctuation
> character are allocated for minor modes. Using them in a major
> mode is not absolutely prohibited, but if you do that, the major
> mode binding may be shadowed from time to time by minor modes.
>
> This means important commands should have a binding reserved for major
> modes. But there is absolutely no need to remove bindings which (for
> many org users) have worked just fine for a long time.
But it's not just a matter of satisfying rules: it's a matter of making
it easy on users. Having a "bad" binding as well as a "good" binding for
something would mean that if I load a minor mode that takes over the
"bad" binding, I would then lose it in the major mode and have to
remember the "good" binding. That's more confusing IMO than having a
single "good" binding: if we need to retrain fingers, we need to retrain
them once, not every time we load a minor mode that steps on some
binding.
I find myself more in agreement with Seb than with Bastien here. The
argument that reducing the number of "bad" bindings reduces the chance
of conflicts does not hold water IMO: we will always have to be looking
in the rear-view mirror for some minor mode that will step on us. If
it's an important enough problem to solve, we should just follow the
emacs guidelines in their entirety.
--
Nick
next prev parent reply other threads:[~2014-01-29 13:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 4:45 org-mode + icicles, avoid key binding redefinitions? Drew Adams
2014-01-23 7:43 ` Bastien
2014-01-23 15:33 ` Drew Adams
2014-01-23 15:46 ` Bastien
2014-01-23 16:28 ` Drew Adams
2014-01-23 16:34 ` Bastien
2014-01-23 17:01 ` Drew Adams
2014-01-23 22:24 ` Bastien
2014-01-23 22:56 ` Drew Adams
2014-01-23 23:29 ` Thomas S. Dye
2014-01-24 8:39 ` Bastien
2014-01-25 7:34 ` Thomas S. Dye
2014-01-28 9:08 ` Bastien
2014-01-29 8:43 ` Sebastien Vauban
2014-01-29 9:39 ` Bastien
2014-01-29 10:35 ` Sebastien Vauban
2014-01-29 11:00 ` Bastien
2014-01-29 11:32 ` Sebastien Vauban
2014-01-29 17:34 ` Thomas S. Dye
2014-01-29 17:48 ` Bastien
2014-01-29 19:48 ` Thomas S. Dye
2014-01-29 20:11 ` Iannis Zannos
2014-01-30 0:39 ` Bastien
2014-01-29 11:44 ` Florian Beck
2014-01-29 13:16 ` Nick Dokos [this message]
2014-01-29 13:52 ` Bastien
2014-01-29 18:01 ` Achim Gratz
2014-01-29 20:06 ` Andreas Leha
2014-01-29 20:13 ` Iannis Zannos
2014-01-29 14:43 ` Florian Beck
2014-01-29 15:40 ` Bastien
2014-01-29 16:20 ` Nicolas Goaziou
2014-01-23 13:57 ` Alan Schmitt
2014-01-23 15:33 ` Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2014-01-18 19:49 John Kitchin
2014-01-18 21:40 ` Alan Schmitt
2014-01-19 15:53 ` Bastien
2014-01-19 17:31 ` Memnon Anon
2014-01-19 20:56 ` John Kitchin
2014-01-20 2:34 ` Memnon Anon
2014-01-20 23:12 ` Alan Schmitt
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3dj6i88.fsf@gmail.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).