jdrouhard

Yeah, that's not what we're trying to do. We have some types with `begin()` and `end()` but we specifically don't want them to be formatted as ranges. Including `fmt/ranges.h` breaks...

I think this is actually an issue in rapidyaml. When you install an error handler via `ryml::Callbacks` that throws (instead of the default abort), it's expected that any kind of...

@biojppm (tagging you in case GitHub notifications are messed up). Anyway, the issue seems to be the always inlined property getters and predicates in `node.hpp`. The functions these forward to...

> `operator[]` is an analogue to the one in `std::vector`, which is non-throwing, and embodies the same spirit, where on optimized builds nothing is checked. Thus, the assert is there...

@BlueDrag0n Most built-in vim commands aren't understood by the parser yet. Most of the tab, buffer, window, and tag related commands aren't understood (like `:tabn[ext]` `:tabp[revious]` `:bn[ext]` `:bp[rev]` `:sp[lit]` `:vert[ical]`...

This issue is for supporting `textDocument/semanticTokens/range`, but the underlying performance/lagginess caused by large responses to the full request should be fixed in HEAD (and the future 0.9.1 bugfix release). Please...

I made some changes: - Reduce the state count and parser size growth - Improved the exportable item stuff a bit - Removed the seemingly unrelated "constants" highlight - Rewrote...

You need to commit all the artifacts from the generate command, not just parser.c.

Probably need to use the tree-sitter binary that would be in `node_modules/...` after you run `npm install`

Sorry @eezstreet ... when it comes to changes the upstream tree-sitter versions make to generated files, I'm not going to be much help. From what I can tell, the ci...