zc he

Another one:   PS. incremental parsing from `true` to `(true)` generates the correct result:  [if statement rule](https://github.com/nushell/tree-sitter-nu/blob/74e6037383ce3a77ed6fdb8281bbd69316c723a4/grammar.js#L1646) If I change the optional repeating [`token.immediate`](https://github.com/nushell/tree-sitter-nu/blob/74e6037383ce3a77ed6fdb8281bbd69316c723a4/grammar.js#L1232) suffix of `(true)` to...

Found some work-around solutions, possibly helpful for debugging this issue. https://github.com/nushell/tree-sitter-nu/pull/167 https://github.com/nushell/tree-sitter-nu/pull/169

I have filed an [issue](https://github.com/tree-sitter/tree-sitter/issues/4558). Appears to be a tree-sitter bug that happens to be triggered by our "crazy" grammar. It's really weird in my opinion, query matching is supposed...

The bug was initially introduced by #139 . Maybe it has something to do with newline characters.

> Though it expected string: > ... Definitely a long existing bug of nu-parser. Probably need a separated issue, if not a duplication. Basically `def t [f: string ] {};...

> > > Though it expected string: > > > ... > > > > Definitely a long existing bug of nu-parser. Probably need a separated issue, if not a...

Could be an issue of blink.cmp though, I can't tell.

@mkatychev, sorry to ping you on an irrelevant PR. I'm confused at the failed CI pipeline, do you happen to know what's going on?

> @blindFS I finally narrowed down the problem, until [tree-sitter/node-tree-sitter#258](https://github.com/tree-sitter/node-tree-sitter/pull/258) is merged, node isn't compatible with 0.25 basically since there's breaking ABI changes that haven't been addressed. > > So...

> ping me when you're ready to land it. Sure