From: Nick Dokos <nicholas.dokos@hp.com>
To: Leo <sdl.web@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Re: Poll: Who is using these commands
Date: Sun, 09 May 2010 11:59:20 -0400 [thread overview]
Message-ID: <3634.1273420760@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Leo <sdl.web@gmail.com> of "Sun, 09 May 2010 15:26:35 BST." <m1pr15jgmc.fsf@cam.ac.uk>
Leo <sdl.web@gmail.com> wrote:
> On 2010-05-09 12:43 +0100, Carsten Dominik wrote:
> > what do you think about C-M-f, C-M-b, C-M-n, C-M-p as alternative
> > bindings? These seem to make *a lot* of sense, because, as many here
> > have pointed out, they are so much better repeatable (Keep C-M- down,
> > press the character.)
>
> It is terrible idea to override these parenthesis movement bindings.
> They are universal in all editing modes that if overridden people who
> also use other emacs packages will be surprised. For example to move
> from a open parenthesis to a closing parenthesis.
>
I disagree: they are not parenthesis movement bindings - they are
structure-navigation bindings. For example, C-M-f is forward-sexp.
In lisp, an sexp has some relationship to parentheses, but it is
incidental; in other programming modes, an sexp is whatever makes
sense in that language and these commands are redefined appropriately.
I think it is entirely appropriate to use these bindings to navigate
structure in org-mode as well.
My 2 cents,
Nick
next prev parent reply other threads:[~2010-05-09 15:59 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 9:14 Poll: Who is using these commands Carsten Dominik
2010-05-08 11:56 ` Vagn Johansen
2010-05-08 12:22 ` Darlan Cavalcante Moreira
2010-05-08 13:28 ` Mikael Fornius
2010-05-08 14:06 ` Bastien
2010-05-08 15:53 ` Eric Schulte
2010-05-08 18:12 ` Benjamin Andresen
2010-05-08 21:47 ` Carsten Dominik
2010-05-08 16:17 ` Memnon Anon
2010-05-08 16:44 ` Sebastian Rose
2010-05-08 17:46 ` Scot Becker
2010-05-08 20:26 ` Stephan Schmitt
2010-05-08 18:04 ` Scott Randby
2010-05-08 22:35 ` Eric S Fraga
2010-05-08 22:46 ` Russell Adams
2010-05-08 20:22 ` Friedrich Delgado Friedrichs
2010-05-08 22:03 ` Scott Randby
2010-05-08 23:42 ` Daniel Clemente
2010-05-09 11:43 ` Carsten Dominik
2010-05-09 12:39 ` Ecce Berlin
2010-05-09 13:08 ` Sebastian Rose
2010-05-09 14:26 ` Leo
2010-05-09 14:42 ` Stephan Schmitt
2010-05-09 15:24 ` Carsten Dominik
2010-05-09 17:27 ` Sebastian Rose
2010-05-09 18:03 ` Leo
2010-05-09 15:59 ` Nick Dokos [this message]
2010-05-09 16:23 ` Leo
2010-05-09 17:33 ` Sebastian Rose
2010-05-09 18:06 ` Leo
2010-05-09 18:13 ` Dan Davison
2010-05-09 18:59 ` Dan Davison
2010-05-09 19:00 ` Dan Davison
2010-05-10 5:07 ` Carsten Dominik
2010-05-09 19:22 ` Scott Randby
2010-05-10 6:33 ` Carsten Dominik
2010-05-11 1:04 ` Scott Randby
2010-05-11 5:22 ` Russell Adams
2010-05-11 8:00 ` Andrew Burrow
2010-05-11 23:45 ` Scott Randby
2010-05-12 1:18 ` Eric Schulte
2010-05-12 2:16 ` Livin Stephen Sharma
2010-05-08 22:21 ` Bernt Hansen
2010-05-08 23:38 ` Sebastian Hofer
2010-05-09 3:28 ` Daniel Martins
2010-05-09 5:10 ` Vincent Belaïche
2010-05-10 8:39 ` Ulf Stegemann
2010-05-10 8:50 ` Jörg Hagmann
2010-05-11 8:13 ` Andrew Burrow
2010-05-11 12:01 ` Matt Lundin
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=3634.1273420760@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=sdl.web@gmail.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.
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).