Previously the `call` helper (and its related functions) returned a `serde_json::Value` which was then decoded either later in the client (see signature help and hover) or by the client's caller. This led to some unnecessary boilerplate in the client: let resp = self.call::<MyRequest>(params); Some(async move { Ok(serde_json::from_value(resp.await?)?) }) and in the caller. It also allowed for mistakes with the types. The workspace symbol request's calling code for example mistakenly decoded a `lsp::WorkspaceSymbolResponse` as `Vec<lsp::SymbolInformation>` - one of the untagged enum members (so it parsed successfully) but not the correct type. With this change, the `call` helper eagerly decodes the response to a request as the `lsp::request::Request::Result` trait item. This is similar to the old helper `request` (which has become redundant and has been eliminated) but all work is done within the same async block which avoids some awkward lifetimes. The return types of functions like `Client::text_document_range_inlay_hints` are now more verbose but it is no longer possible to accidentally decode as an incorrect type. Additionally `Client::resolve_code_action` now uses the `call_with_ref` helper to avoid an unnecessary clone. |
||
---|---|---|
.cargo | ||
.github | ||
book | ||
contrib | ||
docs | ||
helix-core | ||
helix-dap | ||
helix-event | ||
helix-loader | ||
helix-lsp | ||
helix-lsp-types | ||
helix-parsec | ||
helix-stdx | ||
helix-term | ||
helix-tui | ||
helix-vcs | ||
helix-view | ||
runtime | ||
xtask | ||
.envrc | ||
.gitattributes | ||
.gitignore | ||
base16_theme.toml | ||
Cargo.lock | ||
Cargo.toml | ||
CHANGELOG.md | ||
default.nix | ||
flake.lock | ||
flake.nix | ||
grammars.nix | ||
languages.toml | ||
LICENSE | ||
logo.svg | ||
logo_dark.svg | ||
logo_light.svg | ||
README.md | ||
rust-toolchain.toml | ||
rustfmt.toml | ||
screenshot.png | ||
shell.nix | ||
theme.toml |
A Kakoune / Neovim inspired editor, written in Rust.
The editing model is very heavily based on Kakoune; during development I found myself agreeing with most of Kakoune's design decisions.
For more information, see the website or documentation.
All shortcuts/keymaps can be found in the documentation on the website.
Features
- Vim-like modal editing
- Multiple selections
- Built-in language server support
- Smart, incremental syntax highlighting and code editing via tree-sitter
Although it's primarily a terminal-based editor, I am interested in exploring a custom renderer (similar to Emacs) using wgpu or skulpin.
Note: Only certain languages have indentation definitions at the moment. Check
runtime/queries/<lang>/
for indents.scm
.
Installation
Contributing
Contributing guidelines can be found here.
Getting help
Your question might already be answered on the FAQ.
Discuss the project on the community Matrix Space (make sure to join #helix-editor:matrix.org
if you're on a client that doesn't support Matrix Spaces yet).
Credits
Thanks to @jakenvac for designing the logo!