-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Troubleshooting
If you haven't already you should try to check out the helix healthcheck.
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.
Is the LSP server (E.g. rust-analyzer
) in $PATH
?
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: https://github.com/neovim/neovim/wiki/FAQ#esc-in-tmux-or-gnu-screen-is-delayed
Neither Space-p
nor Space-y
is working.
Check that xsel
package is installed in your system.
Check that win32yank.exe
is in your path.
Either download the binaries manually or use scoop (scoop install win32yank
).