From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Python interactive navigation around nested functions
Date: Tue, 21 Jun 2016 02:21:01 -0400 [thread overview]
Message-ID: <jwvtwgn83wq.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 87d1nbdqkn.fsf@secretsauce.net
> 1. If we're on a function-definition line, C-M-a should go up to the
> previous definition, at the SAME OR HIGHER AST level
OK, that's what it's supposed to be already.
> 2. If we're NOT on a function-definition line, C-M-a should go up to the
> previous definition, at a HIGHER AST level.
That's a significant change. It means that if we're between two
functions (e.g. on a static var declaration in a C file), C-M-a would
jump to BOB.
> From any of the "print 55" lines, C-M-h selects the whole "def ddd"
> block, which I would not expect at all. If the ddd block isn't there,
> then it selects all of the "ccc" block, which is wrong too: neither of
> these contain the statement we started on. One could call this a
> separate bug from the original complaint, but changing the C-M-a
> definition makes this work naturally.
These behaviors are indeed problematic (AFAICT they're plain bugs w.r.t
the behavior described in the docstring), but they affect C-M-h, so
hopefully we can fix them in C-M-h without having to change C-M-a.
Of course by C-M-a we can mean different things:
- the backend navigation code provided by the major mode via
*-of-defun-function.
- the command bound to C-M-a.
- the beginning-of-defun command.
They don't do exactly the same thing either, and the constraints w.r.t
changing them are slightly different (e.g. some allow the introduction
of a whole new backend API, or the rebinding of C-M-a to another command).
Stefan
next prev parent reply other threads:[~2016-06-21 6:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 4:52 Python interactive navigation around nested functions Dima Kogan
2016-06-20 2:43 ` Stefan Monnier
2016-06-20 7:14 ` Andreas Röhler
2016-06-20 7:34 ` Stefan Monnier
2016-06-20 8:28 ` Andreas Röhler
2016-06-20 13:57 ` Clément Pit--Claudel
2016-06-20 16:23 ` Andreas Röhler
2016-06-21 5:45 ` Dima Kogan
2016-06-21 6:05 ` Dima Kogan
2016-06-21 6:21 ` Stefan Monnier [this message]
2016-06-24 22:10 ` Dima Kogan
2016-06-24 23:23 ` Clément Pit--Claudel
2016-06-26 19:29 ` Andreas Röhler
2016-06-27 0:39 ` Clément Pit--Claudel
2016-06-27 6:02 ` Andreas Röhler
2016-06-25 0:18 ` Stefan Monnier
2016-06-26 19:37 ` Andreas Röhler
2016-06-21 6:32 ` Andreas Röhler
2016-06-21 6:26 ` Andreas Röhler
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=jwvtwgn83wq.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.