Sergio A. Vargas

Hi @maxbrunsfeld. Bump here. This is good to merge.

This fails for me on some basic expressions: ```jl # generators.jl (x for x in xs) ``` tree-sitter parse generators.jl # master ``` (source_file [0, 0] - [3, 0] (line_comment...

I made the most recent PRs to the repo, so I'd like to give my opinion: I mostly agree with the comments on the linked emacs thread. Using tree-sitter seems...

When I was revising the other literals I left these out because of the following: ``` julia> true === :true true julia> false === :false true julia> nothing === :nothing...

> Just wanted to report a minor issue I found in which sometimes type assertions can be parsed as symbols, see this example @ExpandingMan The PR fixes this 👍 >...

Ok. All the updated rules and their correspoding tests should be ready.

> You should be able to extract the identifiers names, then I guess query the tree for any variable matching that identifier name and value, push that into memory and...

Writing a query like ```scheme ((function_call (identifier) @lushcall (arguments (_) @lushcolor) (eq? @lushcall "hsl"))) @lushcolor ``` in `some_plugin/after/queries/lua/highlights.scm`, and then setting the `lushcolor` highlight would correctly highlight an `hsl` call...

The script looks pretty good. > [...] since it's an separate install you'd just have to maintain both versions anyway, so not much to gain. Yes, this is the thing...

> Tracking variables feels like it could be a maintenance pain Yeah, I probably ignored too many edge cases when I first thought about this feature. > I am wondering...