From: Daniel Colascione <dancol@dancol.org>
To: Jorgen Schaefer <forcer@forcix.cx>
Cc: 13642@debbugs.gnu.org
Subject: bug#13642: 24.3.50; python-nav-backward-sexp mishandles string movement
Date: Wed, 06 Feb 2013 16:12:43 -0800 [thread overview]
Message-ID: <5112F17B.5090808@dancol.org> (raw)
In-Reply-To: <8762250zop.fsf@orion.kollektiv-hamburg.de>
[-- Attachment #1: Type: text/plain, Size: 771 bytes --]
On 2/6/2013 3:50 PM, Jorgen Schaefer wrote:
> Hello!
> In python-mode, I get the following behavior (with _|_ being point):
>
> -----
> def foo():
> bar = "bar"
> baz = "baz"_|_
>
> =>
>
> _|_def foo():
> bar = "bar"
> baz = "baz"
> -----
That's by design. python-mode tries to emulate lisp movement as much as
possible, so it considers point to be at the end of a "defun" and tries to skip
over the entire "defun", back to the beginning.
This functionality appears to be buggy:
def foo():
bar = "bar"
baz = "baz"
x=x()_|_
=>
def foo():
bar = "bar"
baz = "baz"
x=x_|_()
I also find the behavior more counter-intuitive than useful, and I wish
python-mode acted more like cc-mode here.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2013-02-07 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 23:50 bug#13642: 24.3.50; python-nav-backward-sexp mishandles string movement Jorgen Schaefer
2013-02-07 0:12 ` Daniel Colascione [this message]
2013-02-08 21:27 ` Jorgen Schaefer
2013-05-15 5:55 ` Andreas Röhler
2013-02-14 0:31 ` bug#13642: (no subject) Fabián Ezequiel Gallina
2013-02-14 0:47 ` Fabián Ezequiel Gallina
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=5112F17B.5090808@dancol.org \
--to=dancol@dancol.org \
--cc=13642@debbugs.gnu.org \
--cc=forcer@forcix.cx \
/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).