all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 20897@debbugs.gnu.org, Rasmus <rasmus@gmx.us>
Subject: bug#20897: 25.0.50; [python] sexp-movement are confusing
Date: Fri, 04 Feb 2022 00:22:56 +0100	[thread overview]
Message-ID: <877dabk01b.fsf@gmail.com> (raw)
In-Reply-To: <878rurlkpj.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 03 Feb 2022 22:11:04 +0100")

Lars Ingebrigtsen <larsi@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.





      reply	other threads:[~2022-02-03 23:22 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
2022-02-03 23:22   ` Kévin Le Gouguec [this message]

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=877dabk01b.fsf@gmail.com \
    --to=kevin.legouguec@gmail.com \
    --cc=20897@debbugs.gnu.org \
    --cc=larsi@gnus.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.