From: Lars Ingebrigtsen <larsi@gnus.org>
To: Rasmus <rasmus@gmx.us>
Cc: 20897@debbugs.gnu.org
Subject: bug#20897: 25.0.50; [python] sexp-movement are confusing
Date: Thu, 03 Feb 2022 22:11:04 +0100 [thread overview]
Message-ID: <878rurlkpj.fsf@gnus.org> (raw)
In-Reply-To: <87616blr7a.fsf@gmx.us> (rasmus@gmx.us's message of "Thu, 25 Jun 2015 17:53:45 +0200")
Rasmus <rasmus@gmx.us> writes:
> Open test.py
>
> Insert something like this, ignoring point denoted by "{v,^} {1,...,5}".
>
> 4 5 6
> v v v
> def foo(x):
> """return x as one"""
>
> x = 1;
>
> return(x)
> ^ ^ ^
> 2 3 1
>
> Consider points 1,...,5. At point 2 forward-sexp will go to point 1, at
> point 3 backward-sexp will go to point 2. At point 1, sexp-backward will
> go to 4 rather than point 2 (as I would expect). Likewise, at point 4,
> forward sexp goes to point 1 rather than 5. At point five, everything is
> as I would expect, and {forward,backward}-sexp goes to 6 and 4.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Point movement at 2 has been fixed -- it now goes to 3 (in Emacs 29),
not 1.
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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-02-03 21:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 15:53 bug#20897: 25.0.50; [python] sexp-movement are confusing Rasmus
2015-06-25 16:16 ` Andreas Röhler
2015-06-25 16:46 ` Rasmus
2015-06-25 17:23 ` Andreas Röhler
2015-06-26 1:48 ` Stefan Monnier
2015-06-26 2:03 ` Daniel Colascione
2015-06-26 4:19 ` Stefan Monnier
2015-06-26 6:02 ` Andreas Röhler
2015-06-26 6:17 ` Andreas Röhler
2022-02-03 21:11 ` Lars Ingebrigtsen [this message]
2022-02-03 23:22 ` Kévin Le Gouguec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rurlkpj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20897@debbugs.gnu.org \
--cc=rasmus@gmx.us \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.