Michael Davis

It looks like the language server isn't responding to the `textDocument/rangeFormatting` request. Currently we block on this which freezes the editor: https://github.com/helix-editor/helix/blob/ff33b07756548935577aefc15cf48a1beb27b162/helix-term/src/commands.rs#L4602-L4618 Instead the formatting request should probably be handled...

Yep good catch, I believe that's just a copy/paste bug. Feel free to submit a PR. That document lives here: https://github.com/helix-editor/helix/blob/master/book/src/building-from-source.md

~Only the author has unrestricted write access, for everything else we need a PR~ I pushed a commit to remove the bad `--path helix-term` part

\cc @rifoxide what do you think?

#4718 also adds support for multiple tokens. We will most likely merge that PR before we can give this a proper look. If you're resubmitting work from another PR it's...

See https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message#amending-older-or-multiple-commit-messages Rebasing / ammending old commits can be complicated though. We could instead add a co-authored-by tag at merge-time if we squash + merge

Closing in favor of #10996

You can manually test as long as you have a recent enough cargo/rust (I would recommend using [rustup](https://rustup.rs/) for that), `git` and a C/C++ compiler: `cargo run` will start up...

Yeah if the grammar handles new keywords let's add them to the highlights. Otherwise the highlight queries are looking good now :+1:

See the symbol picker for an example of a picker that waits on an LSP request. The workspace symbol picker is maybe also a good example but it's a sort...