GNU bug report logs - #20897
25.0.50; [python] sexp-movement are confusing

Previous Next

Package: emacs;

Reported by: Rasmus <rasmus <at> gmx.us>

Date: Thu, 25 Jun 2015 15:55:02 UTC

Severity: minor

Found in version 25.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Kévin Le Gouguec <kevin.legouguec <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 20897 <at> debbugs.gnu.org, Rasmus <rasmus <at> gmx.us>
Subject: Re: bug#20897: 25.0.50; [python] sexp-movement are confusing
Date: Fri, 04 Feb 2022 00:22:56 +0100
Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> As for the other points here -- that C-M-<right> at 4 shouldn't move to
> 1 -- I think that would be pretty surprising.  That is, these commands
> (try to) move by semantic unit, which is ambiguous in languages like
> Python, so people have differing opinions.  But as far as I can tell,
> python-mode here works as designed, so I'm therefore closing this bug
> report.

FWIW, 28.1 introduces python-forward-sexp-function, which can be set to
nil to have something that is, quoting the Custom tag, more "CC-mode
like".

For older versions, the commentary of python.el suggests an equivalent
way to tweak sexp movement.

I haven't checked if this option satisfies all of the OP's expectations;
still, I figured it was worth mentioning in this thread FTR.




This bug report was last modified 3 years and 167 days ago.

Previous Next


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