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 09:43:03 +0100 [thread overview]
Message-ID: <86lhxz6uw8.fsf@somewhere.org> (raw)
In-Reply-To: 87bnywtqx4.fsf@bzg.ath.cx
Hello Bastien and Thomas,
Bastien wrote:
> thanks for starting this list.
>
> tsd-P0awH739Ni4AvxtiuMwx3w@public.gmane.org (Thomas S. Dye) writes:
>
>> C-c ! Creating timestamps
>> C-c . Creating timestamps
>> C-c # Checkboxes
>> C-c ' Editing and debugging formulas, literal examples, include files,
>> editing source code, cooperation
>> C-c , Priorities
>> C-c ; Comment lines
>> C-c ? Editing and debugging formulas
>> C-c @ Structure editing
>> C-c ^ Structure editing, plain lists, built-in table editor
>> C-c ` Built-in table editor
>> C-c ~ Cooperation
>
> (There is also C-c : (to add QUOTE) but doomed to disappear anyway.)
What about `C-c {' and such in the tables?
> I think most of these keybindings could migrate to a C-c C- version.
>
> For example:
>
> C-c # Checkboxes
>
> would be
>
> C-c C-# Checkboxes
>
> this would work for all of them except C-c ^ beause C-c C-^ is
> already bound to org-up-element. Maybe it can move to C-c M-^
> instead (but that's one of the keybindings that is deeply into
> my memory.)
So is it for me. As half of the above mentioned key bindings -- the
other half, I don't know/use it.
> How would everyone feel about moving those keybindings to comply
> more closely with Emacs coding recommendations?
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.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2014-01-29 8:43 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 [this message]
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
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=86lhxz6uw8.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).