all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Fabián Ezequiel Gallina" <fabian@anue.biz>
Cc: Ivan Andrus <darthandrus@gmail.com>, 11899@debbugs.gnu.org
Subject: bug#11899: 24.1.50; Weird names and unhelpful docstrings for some python function
Date: Fri, 13 Jul 2012 08:20:25 -0400	[thread overview]
Message-ID: <jwvtxxbj1oo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4FFF99D6.6040909@anue.biz> ("Fabián Ezequiel Gallina"'s message of "Fri, 13 Jul 2012 00:45:26 -0300")

>     If something:
>         do_this()
>         do_that()

> If the pointer is at the start of the if statement, and the user issues
> python-nav-forward-sentence he must be taken after the do_that() statement.

That sounds like sexp-based navigation, then.

> python-nav-{backward,forward}-sentence that would navigate blocks of code.

I don't think "sentence" is a good word choice since there is no
accepted meaning of a "sentence" in the context of python code (or code
in general), AFAIK.

If you want to bind these commands to the same keys as
for/backward-sentence, that's fine, but better give them names related
to what they do, rather than to to this key-mapping choice.


        Stefan





  reply	other threads:[~2012-07-13 12:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 14:33 bug#11899: 24.1.50; Weird names and unhelpful docstrings for some python function Ivan Andrus
2012-07-10 22:23 ` Stefan Monnier
2012-07-11  1:14   ` Fabián Ezequiel Gallina
2012-07-11 12:42     ` Ivan Andrus
2012-07-13  3:45       ` Fabián Ezequiel Gallina
2012-07-13 12:20         ` Stefan Monnier [this message]
2012-07-16 13:22           ` Fabián Ezequiel Gallina
2012-07-17 11:08             ` Ivan Andrus
2012-07-17 18:04               ` Fabián Ezequiel Gallina
2012-07-13  5:02   ` Chong Yidong
2012-07-14  2:16     ` Leo

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=jwvtxxbj1oo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11899@debbugs.gnu.org \
    --cc=darthandrus@gmail.com \
    --cc=fabian@anue.biz \
    /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.