emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-mode + icicles, avoid key binding redefinitions?
Date: Wed, 29 Jan 2014 11:35:33 +0100	[thread overview]
Message-ID: <86bnyv2hze.fsf@somewhere.org> (raw)
In-Reply-To: 87lhxzt9dy.fsf@bzg.ath.cx

Bastien,

Bastien wrote:
> "Sebastien Vauban" writes:
>
>> What about `C-c {' and such in the tables?
>
> (FWIW, that's one of the few keybindings I would not like to change.)
>
>> I guess it's better to comply to the Emacs guidelines. That change will
>> allow us to wake up our neurons and fight against Alzheimer. So, let's
>> do it.
>
> Thanks for your feedback -- that said, maybe the move is to big
> compared to the real issue at stake.  I'd rather make this move
> minimalist by just rebinding those keybindings that are not *that*
> into our memories (e.g. C-c # ... )

Personally, I'd opt for a "all-or-none" switch.

If you only do some, we can't rely on "just add another C-" to get the
right key binding. I have the impression we'll never know which ones
were migrated, and which ones weren't.

In the case you don't intend to move 'em all, I'd stay with the current
config, then. Is it really important to have a couple less of "not
standard" key bindings, if we still have others which don't comply?

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2014-01-29 10:35 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 [this message]
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
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=86bnyv2hze.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).