GNU bug report logs - #11899
24.1.50; Weird names and unhelpful docstrings for some python function

Previous Next

Package: emacs;

Reported by: Ivan Andrus <darthandrus <at> gmail.com>

Date: Tue, 10 Jul 2012 14:40:01 UTC

Severity: minor

Found in version 24.1.50

Done: Fabián Ezequiel Gallina <fabian <at> anue.biz>

Bug is archived. No further changes may be made.

Full log


Message #23 received at 11899 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
To: Fabián Ezequiel Gallina <fabian <at> anue.biz>
Cc: Ivan Andrus <darthandrus <at> gmail.com>, 11899 <at> debbugs.gnu.org
Subject: Re: bug#11899: 24.1.50;
	Weird names and unhelpful docstrings for some python function
Date: Fri, 13 Jul 2012 08:20:25 -0400
>     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




This bug report was last modified 13 years and 4 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.