GNU bug report logs - #13642
24.3.50; python-nav-backward-sexp mishandles string movement

Previous Next

Package: emacs;

Reported by: Jorgen Schaefer <forcer <at> forcix.cx>

Date: Wed, 6 Feb 2013 23:53:02 UTC

Severity: normal

Found in version 24.3.50

Done: Fabián Ezequiel Gallina <fabian <at> anue.biz>

Bug is archived. No further changes may be made.

Full log

Message #8 received at 13642 <at> debbugs.gnu.org (full text, mbox):

From: Daniel Colascione <dancol <at> dancol.org>
To: Jorgen Schaefer <forcer <at> forcix.cx>
Cc: 13642 <at> debbugs.gnu.org
Subject: Re: bug#13642: 24.3.50; python-nav-backward-sexp mishandles string
	movement
Date: Wed, 06 Feb 2013 16:12:43 -0800

[Message part 1 (text/plain, inline)]
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.


[signature.asc (application/pgp-signature, attachment)]
This bug report was last modified 12 years and 15 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.