GNU bug report logs - #61374
30.0.50; Wrong mark-sexp with tree-sitter

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Theodor Thornhill <theo <at> thornhill.no>
Cc: 61374 <at> debbugs.gnu.org, spacibba <at> aol.com, casouri <at> gmail.com
Subject: bug#61374: 30.0.50; Wrong mark-sexp with tree-sitter
Date: Thu, 09 Feb 2023 12:52:15 +0200

> From: Theodor Thornhill <theo <at> thornhill.no>
> Cc: spacibba <at> aol.com, casouri <at> gmail.com, 61374 <at> debbugs.gnu.org
> Date: Thu, 09 Feb 2023 10:41:52 +0100
> 
> > Can you show some examples that illustrate these issues?  I'm not sure
> > I follow your line of reasoning, and thus cannot understand the
> > relevant considerations and decisions, and their expected effects on
> > behavior.
> >
> > Thanks.
> 
> 
> consider same code as in the first mail:
> 
> {
>   vector<int> myvar;
> }
> 
> 
> If point is before the first curly, C-M-f will move to after the semi.
> 
> 
> if "compound_statement" is added to the regexps, it will move to after
> the closing curly - all good.
> 
> Now if point is at the c in 'vector', now we will also move to after the
> closing curly, not the first space or after the semi.

Sounds like the treesit sexp movement doesn't have any notion of the
"level" of the sexp or something?  IOW, it doesn't know about the
"innermost" sexp at point?  If so, can we teach treesit.el about that?

Or am I missing the point?

Previous Next

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