060255344c
This splits the `InjectionLanguageMarker::Name` into two: one that preforms the previous behavior (using the language configurations' `injection_regex` fields and performing a match) and a new variant that looks up directly by `language_id` with equality. The old variant is used when capturing the injection language like we do in the markdown queries for codefences. That captured text is part of the document being highlighted so we might need a regex to recognize a language like JavaScript as either "js" or "javascript". But the text passed in the `(#set! injection.language "name")` property can be looked up directly. This property is in the query code so there's no need to be flexible in what we accept: we can require that the `(#set! injection.language ..)` properties refer to languages by their configured ID. This should save a noticeable amount of work for the common case of injections: `(#set! injection.language)` is used much more often than `@injection.language`. |
||
|---|---|---|
| .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!