Closed marcelarie closed 7 months ago
Thanks for the report! We need more hands on this repo. We only have a couple people who've done 99% of the work. Feel free to get your hands dirty and try to submit a PR.
not sure i see the same in Neovim :open_mouth:
I am using neovim too, how strange. Maybe I have some plugin that breaks treesitter.
https://github.com/nushell/tree-sitter-nu/assets/62728887/a38bd21b-3405-488c-977e-ebcdc8cf2611
:scream:
without looking at the config, the only difference i see is the extra export-env
block you have at the top :smirk:
also, do you use the latest version of this TS?
I tried deleting that export-env
and the result is the same:
I use the latest version I think, how can I check it?
fwiw this highlighting looks fine with my neovim config as well.
I use the latest version I think, how can I check it?
not sure, i've installed the queries from this repo manually so i do not have the revision attached to them i fear :confused:
very strange, i just pulled the query file again and reinstalled the TS parser again with the following two scripts:
toolkit update
which calls...install-queries
and i still do not see this :cry:
Did you check the :InspectTree for this?
Cause with my colorscheme this doesn't break the highlight,
however I see an ERROR on this line (26):
| where ($it | str starts-with " ")
right on the where
keyword.
I don't have a solution, but shouldn't there be optional punctuation, like brakets or parenthesis in the _where_predicate here?
where_command: ($) => seq("where", $._where_predicate),
_where_predicate: ($) =>
choice(
...TABLE().map(([precedence, opr]) =>
prec.left(
precedence,
...
Because this:
[["a" "b"];[3 4] [5 6]] | where ("a" < 4)
or this
[["a" "b"];[3 4] [5 6]] | where "a" < 4
breaks it for me also.
where
can have parentheses or braces since it's a closure.
I'm not seeing any errors in the OP's script now (except moving from def-env
to def --env
). So, I'm closing this.
oops, actually I do still see an error. Sorry. @kit494way is this something you'd be interested in fixing?
yes. I will try.
With the
type@'type'
on the command parameter, the syntax highlighting breaks.Example of the code:
Screenshoot: