Helix Editor is a terminal-based modal editor that treats selections as the main editing objects. A cursor belongs to a selection, and commands operate on one or many selected ranges. Helix Editor edits files in buffers; it does not turn the terminal into a graphical project database. Tree-sitter parsing and language servers add structure and code intelligence around those buffers.
Selections come before editing commands
Helix Editor can keep several selections and cursors inside one buffer. Movement commands change the selected ranges, then an edit replaces, deletes or surrounds those ranges. This reverses the usual action-first sequence of many modal editors. A command that looks familiar from another editor may act differently because Helix Editor already has an active selection.
Pickers find files, symbols or search results. They support fuzzy matching and regular-expression filtering. Workspace-symbol text goes to the configured language server, so its results depend on that server’s index. Picker queries do not support an OR operator; separate searches or another regular expression must express alternatives.
Language configuration merges several scopes
Built-in settings, user configuration and a project’s .helix/languages.toml merge into the effective language definition. A project can therefore change a formatter or server without changing every other workspace. After certain server-configuration edits, the running language server needs an LSP restart before it sees the new values.
An external formatter must read the current buffer from standard input and write the formatted result to standard output. A command that only edits a file on disk does not satisfy that contract. Helix Editor then replaces buffer content with the returned text, which can differ from a formatter run against a saved file when unsaved changes exist.
The LSP client does not install servers
Helix Editor can request completion, diagnostics, navigation, rename, code actions and formatting through the Language Server Protocol. The named language-server executable must still be installed and reachable on the system path. Configuration alone cannot supply it.
The hx --health command reports whether a language has its configured server, formatter and syntax components available. Running it for the affected language gives a direct inventory before the user rewrites configuration. That report distinguishes a missing executable from a broken key binding or unsupported request. Inlay hints can still feel slow, and some servers require their own inlay-hint option in addition to the editor setting.
Tree-sitter supplies syntax structure inside the terminal interface, while the external language server supplies project-level semantic information. A formatter follows a third process contract through standard input and output. When highlighting works but rename or completion does not, those paths explain why one feature can succeed while the other remains absent. They also explain why installing one missing server does not install a formatter with another executable name.
