-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Troubleshooting
If you haven't already you should check out the helix healthcheck. Running hx --health <lang>
for a language must print a checkmark for the "Highlight queries" section in order for highlights to work.
If you are not using a package manager to install Helix, then you may have misplaced the required runtime
folder. By default, it should be placed inside the same directory as the executable or inside the system's config directory. This is ~/.config/helix/
on Linux/MacOS, and ~/AppData/Roaming/helix/
on Windows. However, this can be overridden by setting the HELIX_RUNTIME
environment variable to your desired directory.
Additionally, check if the runtime/grammars
folder contains the associated compiled tree-sitter grammar for the language. It should not be empty. If it is, then run hx --grammar fetch
and hx --grammar build
.
Finally, you can open a file for the language missing syntax highlighting, and check your logs with :log-open
.
Features like auto-complete, diagnostics, and goto-definition are driven by LSP. You must have a language's language server installed for these features to work.
If you haven't already you should check out the helix healthcheck. Running hx --health <lang>
for a language must print the language server executable name in green in the "Configured language server" section. Make sure the language server executable is in $PATH
.
If the language server is installed, try starting helix with the -v
flag and checking the log file for LSP related messages.
Both a C and a C++ compiler need to be installed.
The MacOS terminal lacks true color support, so you'll need to install a terminal that has it.
This is because your terminal multiplexer is listening for escape keypresses itself, as part of its own escape sequences, and only passing them to Helix after a delay when it's stopped listening for more keypresses in the sequence. So when you press escape to return to normal mode in Helix, the terminal multiplexer catches it, and only passes it to Helix after the delay.
For changing or disabling the timeout, both tmux.conf and screenrc accept a timeout in milliseconds.
If you don't use escape in your tmux or screen escape sequences, you can disable it:
- For tmux.conf (
~/.tmux.conf
or/etc/tmux.conf
), addset -sg escape-time 0
- For screenrc (
~/.screenrc
or/etc/screenrc
),maptimeout 0
You can also set the timeout to a low value instead:
- For tmux.conf,
set -sg escape-time 10
- For screenrc,
maptimeout 10
For why this doesn't appear to happen in Neovim and Vim, see ESC IN TMUX OR GNU SCREEN IS DELAYED
in Neovim's FAQ.
Neither Space-p
nor Space-y
is working.
In an X session, check that either the xclip
or xsel
package is installed on your system and either of these commands is in your PATH
.
In a Wayland session, check that the wl-clipboard
package is installed on your system and the provided wl-copy
and wl-paste
commands are in your PATH
.
Check that win32yank.exe
is in your Windows path.
Either download the binaries manually or use scoop (scoop install win32yank
).
Trying to yank with the mouse will yank it to the middle mouse clipboard rather than the system clipboard. Clipboards that don't have this secondary clipboard will not have anything yanked.
You may encounter a panic when opening a file that looks like so:
thread 'main' panicked at 'Could not parse queries for language "<language>". Are your grammars out of sync? Try running 'hx --grammar fetch' and 'hx --grammar build'. This query could not be parsed: QueryError { row: 0, column: 17, offset: 17, message: "heading_content", kind: NodeType }', helix-core/src/syntax.rs:377:43
This happens when the tree-sitter queries (.scm
files) in your ~/.config/helix/runtime/queries
directory are out of date with the tree-sitter parsers. To fix this, remove the ~/.config/helix/runtime
directory and link the runtime directory from this repository. Then run hx -g fetch
and hx -g build
.
When starting Helix, you could get the message:
ERROR failed to create instance and plugin env for plugin
displayed instead of the tab-bar and instead of the status-bar.
This could happen because you upgraded Helix from an old version to a much newer version.
The following is known to help:
rm -rf $HOME/.cache/zellij
zellij kill-all-sessions
There is an issue with tmux where the itacic modifier is not shown italic and has a background color instead. Add this to your tmux conf and restart tmux:
set-option -sa terminal-overrides ",xterm*:Tc"
#set -g default-terminal "xterm-256color" # Try this if the line above doesn't work
Some themes do not highlight the primary and secondary selections differently and so you will not see a visible difference. Collapsing the selections with ,
or using a theme that highlights them differently will reveal that the selections are being cycled.