From: Ivan Andrus <darthandrus@gmail.com>
To: 11974@debbugs.gnu.org
Subject: bug#11974: 24.1.50; python-nav-forward-sexp-function doesn't skip over strings
Date: Fri, 28 Sep 2012 23:18:29 +0200 [thread overview]
Message-ID: <51132B81-6D8E-4C01-8BEB-126649B09E4D@gmail.com> (raw)
In-Reply-To: <jwv1uk7qsak.fsf-monnier+emacs@gnu.org>
On Jul 20, 2012, at 12:54 AM, Stefan Monnier wrote:
>>> def foo():
>>> toto
>>> bar
>> In my mind you should skip to after bar only if the cursor is before the def
>> (or possibly anywhere in the def keyword).
>
> This is the obvious non-controversial case, indeed. If that's
> sufficient, then I think there is no remaining problem.
>
> I just assumed that Fabián (or others) also wanted to be able to skip
> just the "block" of statements without the introductory element (like
> def/if/...).
I'm okay if people like the current definition of "sexp" for python-mode, but I still think the implementatin is slightly broken. In the simple example below I cannot get past the end of the main function using `forward-sexp'. Is this by design?
def main():
return 2+3 # I get stuck here
print main()
If this is by design then I'll work around it in my code.
-Ivan
prev parent reply other threads:[~2012-09-28 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 12:29 bug#11974: 24.1.50; python-nav-forward-sexp-function doesn't skip over strings Ivan Andrus
2012-07-19 7:52 ` Stefan Monnier
2012-07-19 19:40 ` Ivan Andrus
[not found] ` <D3BE0B6C-F35A-4E54-A68C-FAB0F92E30D8@gmail.com>
2012-07-19 22:54 ` Stefan Monnier
2012-09-28 21:18 ` Ivan Andrus [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=51132B81-6D8E-4C01-8BEB-126649B09E4D@gmail.com \
--to=darthandrus@gmail.com \
--cc=11974@debbugs.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).