Stephan Seitz

You can try to build release with debug symbols and run a sampling profiler on it. But it will only report on a per-function basis. You can use nvtx to...

@maxxnino @connorlay this is the simplest reproducer for this that we had until now

We discovered that the loading of the highlight/injection queries is indeed happening repeatedly (indent, folding and textobject queries are cached until invalidated by a file change and I thought that...

If the highlights file is maintained here it might be worth to add a wget command to the automatic parser update workflow. So it would also update the query file

I'm not sure what is the best solution. The nvim queries for nvim are a bit different from the Atom ones. Until now most maintainers decided to put the nvim...

`vim-match?` is currently the same as `match?`. At the moment none of the parsers do that. It would make sense for the zig parsers since it already only specialized on...

@clason should we think of this as specialization or try to not forget the issue and add `typedef ... X`/`using X =` for C, `type X ...` in Rust

Sorry, I don't have any experience with Scala. Would you be able to create the relevant query yourself? Do you need assistance? Can you point me to files where this...

This should be fairly straight forward to visualize. `make-range!` has partly be replaced by the ranges that are used in Neovim core for injections. In general the preprocessing function that...

There's a bug in this plugin. You have to create a highlights.scm (even an empty one) to get updates from the highlighting parsers