d8abd1eaf3
* Sort themes by score & then name Previously the themes were appearing unordered after typing ':theme '. This sorts them first by fuzzy score and then by name so that they generally appear in a more ordered fashion in the initial list. The sort by name does not really pay off when there is a score so an alternative approach would be to sort by name if there is string to fuzzy match against and otherwise sort by score. I've lowercased the names as that avoids lower case & upper case letters being sorted into separate groups. There might be a preferable approach to that though. * Sort language & files by score then name And change to use sort_unstable_by instead of sort_unstable_by_key as it allows us to avoid some allocations. I don't fully understand the flow of the 'filename_impl' function but this seems to deliver the desired results. * Remove unnecessary reference Co-authored-by: Michael Davis <mcarsondavis@gmail.com> Co-authored-by: Michael Davis <mcarsondavis@gmail.com> |
2 years ago | |
---|---|---|
.cargo | 2 years ago | |
.github | 2 years ago | |
book | 2 years ago | |
contrib | 2 years ago | |
docs | 2 years ago | |
helix-core | 2 years ago | |
helix-dap | 3 years ago | |
helix-loader | 2 years ago | |
helix-lsp | 2 years ago | |
helix-term | 2 years ago | |
helix-tui | 2 years ago | |
helix-view | 2 years ago | |
runtime | 2 years ago | |
xtask | 2 years ago | |
.envrc | 3 years ago | |
.gitignore | 2 years ago | |
CHANGELOG.md | 3 years ago | |
Cargo.lock | 2 years ago | |
Cargo.toml | 3 years ago | |
LICENSE | 4 years ago | |
README.md | 3 years ago | |
VERSION | 3 years ago | |
base16_theme.toml | 2 years ago | |
default.nix | 2 years ago | |
flake.lock | 2 years ago | |
flake.nix | 2 years ago | |
grammars.nix | 2 years ago | |
languages.toml | 2 years ago | |
rust-toolchain.toml | 3 years ago | |
rustfmt.toml | 3 years ago | |
screenshot.png | 3 years ago | |
shell.nix | 2 years ago | |
theme.toml | 2 years ago |
README.md
Helix
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
Packages are available for various distributions (see Installation docs).
If you would like to build from source:
git clone https://github.com/helix-editor/helix
cd helix
cargo install --path helix-term
This will install the hx
binary to $HOME/.cargo/bin
and build tree-sitter grammars.
If you want to customize your languages.toml
config,
tree-sitter grammars may be manually fetched and built with hx --grammar fetch
and hx --grammar build
.
Helix also needs its runtime files so make sure to copy/symlink the runtime/
directory into the
config directory (for example ~/.config/helix/runtime
on Linux/macOS, or %AppData%/helix/runtime
on Windows).
OS | command |
---|---|
windows | xcopy runtime %AppData%/helix/runtime |
linux/macos | ln -s $PWD/runtime ~/.config/helix/runtime |
This location can be overridden via the HELIX_RUNTIME
environment variable.
Packages already solve this for you by wrapping the hx
binary with a wrapper
that sets the variable to the install dir.
NOTE: running via cargo also doesn't require setting explicit
HELIX_RUNTIME
path, it will automatically detect theruntime
directory in the project root.
In order to use LSP features like auto-complete, you will need to install the appropriate Language Server for a language.
MacOS
Helix can be installed on MacOS through homebrew via:
brew tap helix-editor/helix
brew install helix
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).