From: Tim Loderhose <tim@loderhose.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 72034@debbugs.gnu.org
Subject: bug#72034: 29.3; python-ts-mode navigation fails
Date: Mon, 15 Jul 2024 09:54:05 +0000 [thread overview]
Message-ID: <I3RXfZ8dDAxnOcbXAaN2WckgYHbQJ6x649Zg-u-h1qsIUhlPt0F0RLP1QEnfRTk64b2sJ0C5FQJMq7qhuECOS_7hQI7q2uYcai3u4c9Y2jE=@loderhose.com> (raw)
In-Reply-To: <864j8xo36v.fsf@gnu.org>
I just built the latest emacs-30, and indeed the problem appears to be fixed there!
On Wednesday, July 10th, 2024 at 2:13 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Wed, 10 Jul 2024 09:45:01 +0000
> > From:
> >
> > Tim
> >
> > Loderhose tim@loderhose.com
> >
> > python-nav-forward-defun doesn't work properly in python-ts-mode, for
> > example with this file:
> > https://raw.githubusercontent.com/timlod/onset-fingerprinting/6c8f9bd3b82398c9af3519036e0d5a550ad3bae7/onset_fingerprinting/data.py
> >
> > Specifically, at some point it will stop navigating, even though there
> > are still function definitions to traverse (other times I saw it skipped
> > some definitions before stopping altogether). I noticed that this
> > usually happens after some point in the buffer, but I haven't been able
> > to nail it down exactly. My hunch is that it could be related to
> > decorators (e.g. @classmethod) or type hints, or both.
>
>
> I can reproduce this in Emacs 29, but not on the current emacs-30
> release branch, which will eventually become Emacs 30. So I guess we
> already fixed that meanwhile. Can you try building the development
> code of Emacs and see if the problem goes away?
>
> Thanks.
next prev parent reply other threads:[~2024-07-15 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 9:45 bug#72034: 29.3; python-ts-mode navigation fails Tim Loderhose
2024-07-10 12:13 ` Eli Zaretskii
2024-07-15 9:54 ` Tim Loderhose [this message]
2024-07-15 11:03 ` Eli Zaretskii
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='I3RXfZ8dDAxnOcbXAaN2WckgYHbQJ6x649Zg-u-h1qsIUhlPt0F0RLP1QEnfRTk64b2sJ0C5FQJMq7qhuECOS_7hQI7q2uYcai3u4c9Y2jE=@loderhose.com' \
--to=tim@loderhose.com \
--cc=72034@debbugs.gnu.org \
--cc=eliz@gnu.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 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.