From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>, "Yuan Fu" <casouri@gmail.com>
Cc: 65810@debbugs.gnu.org
Subject: bug#65810: 30.0.50; C-M-f and related functions error out in c++-ts-mode
Date: Thu, 07 Sep 2023 21:09:33 +0300 [thread overview]
Message-ID: <83wmx1yhwi.fsf@gnu.org> (raw)
In-Reply-To: <87bkedlvs8.fsf@gmail.com> (message from João Távora on Thu, 07 Sep 2023 18:48:07 +0100)
> From: João Távora <joaotavora@gmail.com>
> Cc: eliz@gnu.org
> Date: Thu, 07 Sep 2023 18:48:07 +0100
>
> Now just type C-M-f or any C-M-something command.
>
> Debugger entered--Lisp error: (treesit-invalid-predicate nil)
> treesit-node-match-p(#<treesit-node "{" in 1-2> sexp t)
> #f(compiled-function (node) #<bytecode 0x1a160a6a590699e2>)(#<treesit-node "{" in 1-2>)
> treesit-node-match-p(#<treesit-node "{" in 1-2> #f(compiled-function (node) #<bytecode 0x1a160a6a590699e2>) t)
> treesit-node-top-level(#<treesit-node "{" in 1-2> #f(compiled-function (node) #<bytecode 0x1a160a6a590699e2>) t)
> treesit--things-around(5 sexp)
> treesit--navigate-thing(5 -1 beg sexp restricted)
> treesit-beginning-of-thing(sexp 1 restricted)
> treesit-forward-sexp(-1)
> forward-sexp(-1 nil)
> forward-sexp(-1 5)
> backward-sexp(1 5)
> funcall-interactively(backward-sexp 1 5)
> call-interactively(backward-sexp nil nil)
> command-execute(backward-sexp)
>
> simple.cpp can be any C++ file, from a simple
>
> int main() {return 0;}
>
> to a completely empty file.
With the above sample file I can indeed reproduce the error. But not
with real-life files I tried, where functions are larger and there's
usually more than one function.
Yuan, could you please look into this?
next prev parent reply other threads:[~2023-09-07 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 17:48 bug#65810: 30.0.50; C-M-f and related functions error out in c++-ts-mode João Távora
2023-09-07 18:09 ` Eli Zaretskii [this message]
2023-09-07 23:12 ` Yuan Fu
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=83wmx1yhwi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65810@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=joaotavora@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).