From: Yuan Fu <casouri@gmail.com>
To: Gonzalo Larumbe <gonzalomlarumbe@gmail.com>
Cc: 72359@debbugs.gnu.org
Subject: bug#72359: treesit-node-at-point bug on vhdl-ts-mode after update to 0.22.6
Date: Tue, 27 Aug 2024 01:22:42 -0700 [thread overview]
Message-ID: <82E11A08-D216-4947-8947-2FB99558F6C1@gmail.com> (raw)
In-Reply-To: <CADYqLo9imi3kG4xyfH8buuw4QyNNNoWuMTtmDJkpmzYHmQxv6Q@mail.gmail.com>
> On Jul 29, 2024, at 3:17 PM, Gonzalo Larumbe <gonzalomlarumbe@gmail.com> wrote:
>
> Hi,
>
> After updating tree-sitter on Arch Linux from 0.22.1 to 0.22.6 there seems to be an error with the detection of some comment nodes under `vhdl-ts-mode`.
>
> In the attached VHDL file, if placing the cursor at the comment of line 10, running:
> `(treesit-node-at (point) 'vhdl)` returns `#<treesit-node block_header in 329-358>`. However, the side by side view shows that the parser correctly detects a comment (see attached screenshot). This worked well with the previous tree-sitter version.
> Thanks a lot!
>
> Gonzalo
>
> <treesit-vhdl-bug.vhdl><treesit-bug.PNG>
Thank you for your report, Gonzalo! And sorry for the delay. I properly looked into this today, and confirmed that this is a tree-sitter bug. I raised an issue here: https://github.com/tree-sitter/tree-sitter/issues/3555
Sadly, there’s not much we can do right now. There was another similar bug in tree-sitter, which I worked around by using another function. But now that “another function” is also broken, oh well :-(
Yuan
next prev parent reply other threads:[~2024-08-27 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 22:17 bug#72359: treesit-node-at-point bug on vhdl-ts-mode after update to 0.22.6 Gonzalo Larumbe
2024-08-27 8:22 ` Yuan Fu [this message]
2024-08-29 12:07 ` Eli Zaretskii
2024-09-02 17:59 ` Yuan Fu
2024-09-13 11:50 ` Gonzalo Larumbe
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=82E11A08-D216-4947-8947-2FB99558F6C1@gmail.com \
--to=casouri@gmail.com \
--cc=72359@debbugs.gnu.org \
--cc=gonzalomlarumbe@gmail.com \
/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).