all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: "Ivan Andrus" <darthandrus@gmail.com>,
	"Fabián E. Gallina" <fabian@anue.biz>,
	11899@debbugs.gnu.org
Subject: bug#11899: 24.1.50; Weird names and unhelpful docstrings for some python function
Date: Fri, 13 Jul 2012 13:02:33 +0800	[thread overview]
Message-ID: <87y5mogsnq.fsf@gnu.org> (raw)
In-Reply-To: <jwvipdvntno.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 10 Jul 2012 18:23:57 -0400")

Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

>>   python-nav-sentence-start
>>   python-nav-sentence-end
>>   python-nav-forward-sentence
>>   python-nav-backward-sentence
>> have weird names in the sense that they don't move by sentences.
>
> Indeed, thanks for catching that.  Fabián, can you take a look at it?

For consistency with the rest of the Emacs code base, I suggest dropping
the `nav', since other modes don't use that naming convention.  As for
the bug report, I don't have an opinion on whether it should be
`python-sentence-start' or `python-statement-start'.  If the former, it
would be nice if the docstring explains what "sentence" means in the
Python context.





  parent reply	other threads:[~2012-07-13  5:02 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
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 [this message]
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=87y5mogsnq.fsf@gnu.org \
    --to=cyd@gnu.org \
    --cc=11899@debbugs.gnu.org \
    --cc=darthandrus@gmail.com \
    --cc=fabian@anue.biz \
    --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 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.