From: Rasmus <rasmus@gmx.us>
To: 20897@debbugs.gnu.org
Subject: bug#20897: 25.0.50; [python] sexp-movement are confusing
Date: Thu, 25 Jun 2015 18:46:46 +0200 [thread overview]
Message-ID: <87wpyrka6h.fsf@gmx.us> (raw)
In-Reply-To: <87616blr7a.fsf@gmx.us>
Hi,
Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>> Sexp movement in python.el are very confusing to me. I know that logical
>> sexp movements outside lisp are subjective,
>
> Not more as anything else editor-related. Languages are composed by
> elements, which a syntax may describe. Even if an editor must not be
> the slave of a syntax, it should be aware of.
That is probably true. I really just want to be able to bent python.el to
work with my internal "fast" logic which controls how I type on keyboard.
>> and I know that the behavior
>> isn't wrong.
>
> It behaves arbitrary WRT Python syntax, that's wrong.
OK. I'm not sure. I can somehow imagine parentheses that would justify
the movements cf. below. But in lisp it would not go from one "nesting"
to another, which is essentially what bugs me.
> Python is composed by expressions.
> If inside an expression C-M-f should to to its end.
>
> From end to next end same level if existing - or level up, or next
> top-level-form, or nil at EOB
>
> Backward and forward needs to be consistent.
I'm not sure I understand.
The way I think about it is like the following. If I'm at point 2 and
move backward I really want to be a point 1. But in python point 0 and 1
is the same, so it assumes the outer level which has end point 4. But I
at most want to go to point 3, closing the "nearest" "sexp".
01 2 3
vv v V
((defun name (arg))
...)
^
4
Rasmus
--
Don't panic!!!
next prev parent reply other threads:[~2015-06-25 16:46 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpyrka6h.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=20897@debbugs.gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).