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 #29 received at 20897 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Röhler <andreas.roehler <at> easy-emacs.de>
To: Daniel Colascione <dancol <at> dancol.org>, 
 Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Cc: 20897 <at> debbugs.gnu.org
Subject: Re: bug#20897: 25.0.50; [python] sexp-movement are confusing
Date: Fri, 26 Jun 2015 08:17:14 +0200
Am 26.06.2015 um 04:03 schrieb Daniel Colascione:
> On 06/25/2015 09:48 PM, Stefan Monnier wrote:
>>> If inside an expression C-M-f should to to its end.
>> No, as explained elsewhere, C-M-f's binding is a binding that goes to
>> the end of the expression that immediately *follows* point.  If we're
>> *inside* a sexp, the way to jump to its end is up-list.
>>
>> I understand you want/like to jump to the end of the enclosing
>> expression, and that's fine, but this is not what C-M-f should do
>> by default.
> "Right" or "wrong" aside, Python's current default behavior is just
> inconsistent with other modes for infix-expression languages. I tried
> for a long time to use the default behavior --- maybe there was some
> efficiency advantage that would take time to appear --- but I ended up
> just giving up and making python-mode work like other modes.
>

Just to give an example syntax-oriented doesn't mean being enslaved by 
syntax: operators in Python are expressions, but sexp should jump over, 
as symbol-at-point is available.  In case some more specific is needed, 
py-partial-expression is delivered.




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

Previous Next


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