From: Antoine Levitt <antoine.levitt@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Binding M-n and M-p to forward-paragraphandbackward-paragraphrespectively
Date: Fri, 08 Apr 2011 12:19:06 +0200 [thread overview]
Message-ID: <871v1d82qt.fsf_-_@gmail.com> (raw)
In-Reply-To: 4D9E3AFF.2080301@harpegolden.net
08/04/11 00:30, David De La Harpe Golden
> On 07/04/11 21:31, Antoine Levitt wrote:
>
>> I've got this bound globally as well. It just makes sense with the
>> global idea that C- is for atomic movements, and M- for group
>> movement.
>
> Er. In this particular case, M-{ and M-} are already conveniently
> bound to the movement by paragraph functions (and C-up/C-down...),
> anyway, aren't they? Certain non-us keyboard layouts make '{' and '}'
> harder to type I suppose, but do we really need a third pair of
> bindings for the same damn actions? Hell, I tend to think of the
> C-up/C-down one as less than useful, but I expect I edit bulk natural
> language text in emacs a lot less than some users.
Ah, yes, that's a good point. I use a french keyboard layout where M-{}
is a pain to type, so I missed that. But since emacs pretty much assumes
a US layout and paragraph functions are already bound to those, there's
no sense in binding them to M-n and M-p additionally.
next prev parent reply other threads:[~2011-04-08 10:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 13:57 Binding M-n and M-p to forward-paragraph and backward-paragraph respectively Deniz Dogan
2011-04-07 16:33 ` Binding M-n and M-p to forward-paragraph and backward-paragraphrespectively Drew Adams
2011-04-07 17:57 ` Sean Sieger
2011-04-07 18:15 ` Binding M-n and M-p to forward-paragraph andbackward-paragraphrespectively Drew Adams
2011-04-07 18:24 ` Sean Sieger
2011-04-07 18:28 ` Binding M-n and M-p to forward-paragraphandbackward-paragraphrespectively Drew Adams
2011-04-07 18:29 ` Sean Sieger
2011-04-07 20:31 ` Antoine Levitt
2011-04-07 20:53 ` Binding M-n and M-p toforward-paragraphandbackward-paragraphrespectively Drew Adams
2011-04-08 3:13 ` Davis Herring
2011-04-08 8:09 ` Andreas Röhler
2011-04-07 22:30 ` Binding M-n and M-p to forward-paragraphandbackward-paragraphrespectively David De La Harpe Golden
2011-04-08 10:19 ` Antoine Levitt [this message]
2011-04-08 21:48 ` Lennart Borgman
2011-04-09 1:40 ` Binding M-n and M-p to forward-paragraph and backward-paragraph respectively Stefan Monnier
2011-04-09 4:10 ` chad
2011-04-09 15:24 ` Binding M-n and M-p to forward-paragraph and backward-paragraphrespectively Drew Adams
2011-04-09 19:09 ` chad
2011-04-09 19:26 ` Drew Adams
2011-04-10 2:49 ` Leo
2011-04-10 3:10 ` chad
2011-04-10 5:37 ` Leo
2011-04-10 9:15 ` Stephen J. Turnbull
2011-04-10 13:17 ` Lennart Borgman
2011-04-09 21:29 ` Davis Herring
2011-04-09 22:50 ` PJ Weisberg
2011-04-09 19:30 ` Binding M-n and M-p to forward-paragraph and backward-paragraph respectively Chong Yidong
2011-04-10 3:33 ` Stefan Monnier
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=871v1d82qt.fsf_-_@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=emacs-devel@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.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).