From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Re: movement bindings in c-mode
Date: Fri, 27 Jun 2008 21:49:27 +0000 [thread overview]
Message-ID: <20080627214927.GB3809@muc.de> (raw)
In-Reply-To: <87zlpc6lsx.fsf@localhorst.mine.nu>
Hi, David!
On Mon, Jun 23, 2008 at 08:36:14PM +0200, David Hansen wrote:
> On Mon, 23 Jun 2008 17:05:53 +0000 Alan Mackenzie wrote:
> > Just one small point, though. The doc-string for
> > beginning-of-defun-function recommends putting point at the { rather
> > than the function header. I think this is unright. Stefan?
> Actually I would prefer to have it in front of the `{'. If you just
> want to read something around the b-o-d it doesn't matter.
It matters, I think, when you do C-x n d. Then you can see what
function you're within.
> But if you want to edit something it's far more likely that it is within
> the body, e.g. adding a variable, than the header.
I'd conjecture that any line within a defun is as likely to be edited as
any other. That you've got an extra 3 or 4 lines to move forward to
that point doesn't seem that critical.
But I think the critical reason is that the command is called
beginning-of-defun, not beginning-of-defun-block, and commands should do
what they say. It would be possible to modify b-o-d so that a bare
prefix (C-u) would go to the block rather than the header. But I don't
think it would be worth the extra complication.
> David
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-06-27 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 8:37 movement bindings in c-mode Miles Bader
2008-06-23 14:13 ` Alan Mackenzie
2008-06-23 13:57 ` Miles Bader
2008-06-23 14:09 ` Miles Bader
2008-06-23 17:05 ` Alan Mackenzie
2008-06-23 18:36 ` David Hansen
2008-06-23 18:40 ` Lennart Borgman (gmail)
2008-06-27 21:50 ` Alan Mackenzie
2008-06-27 21:49 ` Alan Mackenzie [this message]
2008-06-23 18:45 ` Stefan Monnier
2008-06-24 2:32 ` Miles Bader
2008-06-27 21:41 ` Alan Mackenzie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080627214927.GB3809@muc.de \
--to=acm@muc.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.