From b81b285d92d569ac13f66af4cbcf1a9421745ad4 Mon Sep 17 00:00:00 2001 From: Ryan Yin Date: Thu, 28 Dec 2023 14:34:15 +0800 Subject: [PATCH] feat: zellij + yazi + helix --- home/base/server/helix/README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/home/base/server/helix/README.md b/home/base/server/helix/README.md index 0df5fcd2..3d2f64ae 100644 --- a/home/base/server/helix/README.md +++ b/home/base/server/helix/README.md @@ -16,4 +16,15 @@ Whether I'll switch my main editor to Helix or not, it gives me a lot of ideas o 1. 1. 1. **My Neovim often gets stuck when I switch to [toggleterm.nvim](https://github.com/akinsho/toggleterm.nvim), this Helix issue made me consider to switch from this neovim plugin to zellij**. +1. Helix do not have a tree-view panel, it's recommended to use yazi/rangeer/broot instead, and open helix in them. + 1. a tree-view plugin may be added after the plugin system is stable, but no one knows when it will be. + 2. and some helix users stated that they don't need a tree-view plugin, helix's file picker is +1. It seems Helix lacks a substitution command, you should run it in another window(via wm or zellij). + 1. Neovim's substitution command allow you to preview the changes before you apply it, and it's very useful. if I switch to Helix, I'll need to find some other tools with similar feature(such as https://github.com/ms-jpq/sad). + 2. The downside of Neovim's substitution command is that it's unable to save the command we just typed. If I made some things wrong, I have to type the whole substitution command again. + +I think Use Helix/Neovim within a terminal file manager(zellij/ranger/broot) and zellij is a good idea. +It's quite different from the workflow I migrated from VSCode/Jetbrains before, I'm very interested in it. + +In Neovim I can make the workflow similar to VSCode/Jetbrains by using some plugins, but Helix forces me to get out of my comfort zone, and try something new.