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


View this message in rfc822 format

From: Ivan Andrus <darthandrus <at> gmail.com>
To: Fabián Ezequiel Gallina <fabian <at> anue.biz>
Cc: Stefan Monnier <monnier <at> IRO.UMontreal.CA>, 11899 <at> debbugs.gnu.org
Subject: bug#11899: 24.1.50; Weird names and unhelpful docstrings for some python function
Date: Tue, 17 Jul 2012 13:08:29 +0200
On Jul 16, 2012, at 3:22 PM, Fabián Ezequiel Gallina wrote:
> On 07/13/2012 09:20 AM, Stefan Monnier wrote:
>>>     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
> I just pushed some new navigation commands with proper documentation and names. Also there's a specialized forward-sexp-function included.
> 
> All of this is included in revno 109105.

Excellent.  Thanks.

-Ivan



This bug report was last modified 12 years and 313 days ago.

Previous Next


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