unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: "Stefan Monnier" <monnier@IRO.UMontreal.CA>,
	"Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 20897@debbugs.gnu.org
Subject: bug#20897: 25.0.50; [python] sexp-movement are confusing
Date: Thu, 25 Jun 2015 22:03:36 -0400	[thread overview]
Message-ID: <558CB2F8.4060600@dancol.org> (raw)
In-Reply-To: <jwvfv5fw8bi.fsf-monnier+emacsbugs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 814 bytes --]

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.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-06-26  2:03 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 [this message]
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=558CB2F8.4060600@dancol.org \
    --to=dancol@dancol.org \
    --cc=20897@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=monnier@IRO.UMontreal.CA \
    /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).