GNU bug report logs - #40563
28.0.50; Narrow to defun in python buffer

Previous Next

Package: emacs;

Reported by: Tomas Nordin <tomasn <at> posteo.net>

Date: Sat, 11 Apr 2020 22:53:01 UTC

Severity: normal

Tags: fixed

Found in version 28.0.50

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


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

From: Tomas Nordin <tomasn <at> posteo.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 40563 <at> debbugs.gnu.org
Subject: Re: bug#40563: 28.0.50; Narrow to defun in python buffer
Date: Tue, 01 Dec 2020 22:05:14 +0100
Tomas Nordin <tomasn <at> posteo.net> writes:

> Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
>> Tomas Nordin <tomasn <at> posteo.net> writes:
>>
>>> I then noticed that placing point just below the class definition and
>>> then narrow works as expected. But I think the recipe way should work as
>>> well. And even if not, this behavior is confusing.
>>
>> This bug is still present on the trunk.
>>
>> The problem is most easily reproduced by calling the
>>
>>   (python-nav--beginning-of-defun)
>>
>> function directly.  If point is on the first line, then this function
>> won't do the right thing:
>>
>> def a1(self):
>>     pass
>>
>
> It does the right thing here (still on the same build) when point is at
> column > 4, and the wrong thing when at 4 or less. Indentation?

Or I said wrong, now my version is 28.0.50 2020-06-07.




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

Previous Next


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