From: Gilaras Drakeson <gilaras@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Similar key bindings for moving among tags in sgml and nxml modes?
Date: Fri, 27 Nov 2009 12:07:07 -0500 [thread overview]
Message-ID: <86aay7gamc.fsf@gmail.com> (raw)
In-Reply-To: 87skc2p11k.fsf@catnip.gol.com
...
> No, adding different key bindings is the wrong way. The right way is to
> make emacs sexp-movement commands (which are even already bound globally
> to the keys you suggest) work properly in nxml-mode .
>
> ... and in fact, that's already supported!
>
> Just do: (setq nxml-sexp-element-flag t)
>
> [I think that should even be the default, but what do I know...]
In addition, I would vote for paredit keybindings, too.
--
Gilaras
prev parent reply other threads:[~2009-11-27 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 0:16 Similar key bindings for moving among tags in sgml and nxml modes? Lennart Borgman
2009-11-26 0:44 ` Miles Bader
2009-11-26 1:32 ` Lennart Borgman
2009-11-27 17:07 ` Gilaras Drakeson [this message]
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=86aay7gamc.fsf@gmail.com \
--to=gilaras@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).