How I'm Using Helix Editor

Summary

I've been using Helix as my editor to develop on remote servers for quite some time now.There are a lot of emerging supply-chain attacks, and I simply don't like the idea of installing tens of plugins to Vim/Neovim to make the editor usable.To make the switch from Neovim easier, I had to make some changes to the configuration. I want to share them to save you some time, because discovering them is not straightforward.Tmux setupI use tmux as a terminal multiplexer.One thing that I miss from Neovim setup is a good file manager and TUI for git. I rarely use a file manager, but when I need to, I usually want to move a bunch of selected files quickly. Unfortunately, Helix does not support file editing in the explorer. You can only view them.To overcome it, I added new keybindings to my tmux config:# Yazi related set -g allow-passthrough on set -ga update-environment TERM set -ga update-environment TERM_PROGRAM bind-key y display-popup -d '#{pane_current_path}' -x R -h 95% -w 95% -E 'tmux new-session yazi \; set status off' bind-key g popup -E -w 95% -h 95% -d '#{pane_current_path}' lazygit bind-key e display-popup -w 95% -h 90% -E "tmux capture-pane -Jp -S- | hx -" When I hit one of the keys, a new pop-up window opens.prefix - y - opens yazi file managerprefix - g - opens lazygitprefix - e - opens Helix editor with tmux output history.The default prefix for tmux is Ctrl + b, but I'm using Ctrl + \.The last binding is useful when you want to work with terminal output in your editor. I use it to search the history using regexes or copy selected output quickly. For example, I use it quite a lot to copy output from clickhouse client that outputs SQL results in CSV or JSON to the terminal. Although it can output it to a file, that's an extra step, since I usually only need to copy-paste the output to Slack. This can be done via mouse, but painful with tmux setup, since you need to scroll the buffer when the output does not fit in one screen.The yazi and lazygit tools are usua...