515ef17207
Diagnostics are currently extended if text is inserted at their end. This is
desirable when inserting text after an identifier. For example consider:
let foo = 2;
--- unused variable
Renaming the identifier should extend the diagnostic:
let foobar = 2;
------ unused variable
This is currently implemented in helix but as a consequence adding whitespaces
or a type hint also extends the diagnostic:
let foo = 2;
-------- unused variable
let foo: Bar = 2;
-------- unused variable
In these cases the diagnostic should remain unchanged:
let foo = 2;
--- unused variable
let foo: Bar = 2;
--- unused variable
As a heuristic helix will now only extend diagnostics that end on a word char
if new chars are appended to the word (so not for punctuation/ whitespace).
The idea for this mapping was inspired for the word level tracking vscode uses
for many positions. While VSCode doesn't currently update diagnostics after
receiving publishDiagnostic it does use this system for inlay hints for example.
Similarly, the new association mechanism implemented here can be used for word
level tracking of inlay hints.
A similar mapping function is implemented for word starts. Together
these can be used to make a diagnostic stick to a word. If that word
is removed that diagnostic is automatically removed too. This is the exact
same behavior VSCode inlay hints eixibit.
|
11 months ago | |
|---|---|---|
| .cargo | 2 years ago | |
| .github | 11 months ago | |
| book | 11 months ago | |
| contrib | 1 year ago | |
| docs | 11 months ago | |
| helix-core | 11 months ago | |
| helix-dap | 11 months ago | |
| helix-event | 11 months ago | |
| helix-loader | 11 months ago | |
| helix-lsp | 11 months ago | |
| helix-parsec | 11 months ago | |
| helix-term | 11 months ago | |
| helix-tui | 11 months ago | |
| helix-vcs | 11 months ago | |
| helix-view | 11 months ago | |
| runtime | 11 months ago | |
| xtask | 11 months ago | |
| .envrc | 12 months ago | |
| .gitattributes | 2 years ago | |
| .gitignore | 2 years ago | |
| .ignore | 1 year ago | |
| CHANGELOG.md | 1 year ago | |
| Cargo.lock | 11 months ago | |
| Cargo.toml | 11 months ago | |
| LICENSE | 4 years ago | |
| README.md | 11 months ago | |
| base16_theme.toml | 2 years ago | |
| default.nix | 2 years ago | |
| flake.lock | 11 months ago | |
| flake.nix | 11 months ago | |
| grammars.nix | 1 year ago | |
| languages.toml | 11 months ago | |
| logo.svg | 11 months ago | |
| logo_dark.svg | 2 years ago | |
| logo_light.svg | 2 years ago | |
| rust-toolchain.toml | 12 months ago | |
| rustfmt.toml | 3 years ago | |
| screenshot.png | 3 years ago | |
| shell.nix | 2 years ago | |
| theme.toml | 2 years ago | |
README.md
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
It's a terminal-based editor first, but I'd like to explore a custom renderer (similar to Emacs) in 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!