From: Tomas Nordin <tomasn@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 40563@debbugs.gnu.org
Subject: bug#40563: 28.0.50; Narrow to defun in python buffer
Date: Tue, 01 Dec 2020 22:05:14 +0100 [thread overview]
Message-ID: <87k0u1w839.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87mtyxw895.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me>
Tomas Nordin <tomasn@posteo.net> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Tomas Nordin <tomasn@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.
next prev parent reply other threads:[~2020-12-01 21:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 22:52 bug#40563: 28.0.50; Narrow to defun in python buffer Tomas Nordin
2020-10-26 13:57 ` Lars Ingebrigtsen
2020-12-01 21:01 ` Tomas Nordin
2020-12-01 21:05 ` Tomas Nordin [this message]
2020-12-04 7:48 ` Andreas Röhler
2020-12-13 13:32 ` Tomas Nordin
2020-12-14 16:00 ` Lars Ingebrigtsen
2020-12-14 19:38 ` Tomas Nordin
2020-12-14 20:03 ` Lars Ingebrigtsen
2020-12-14 22:18 ` Tomas Nordin
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0u1w839.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me \
--to=tomasn@posteo.net \
--cc=40563@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).