diff options
Diffstat (limited to 'content/blog/trying-out-helix.md')
| -rw-r--r-- | content/blog/trying-out-helix.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/content/blog/trying-out-helix.md b/content/blog/trying-out-helix.md index f7fd503..79fbc7b 100644 --- a/content/blog/trying-out-helix.md +++ b/content/blog/trying-out-helix.md @@ -25,7 +25,7 @@ alias hx="helix" Helix comes pre installed with LSP support, color schemes, a fuzzy finder similar to telescope, native syntax tree with tree sitter, auto closing characters such as brackets, parenthesis and quotes and more. -Helix and [Neovim](https://neovim.io) feel different to me, because with Neovim, I spend more time making the **perfect** configuration instead of having work done. With Helix you have almost nothing to setup. Some people might say that compared to Neovim/Vim, Helix is bloated, but I really think that this 'bloat' feels awesome and will find it's own audience. +Helix are different [Neovim](https://neovim.io) as helix works out of the box, you have nothing to configure. Some people might say that compared to Neovim/Vim, Helix is bloated, but I really think that this 'bloat' feels awesome and will find it's own audience. ### Conf @@ -33,14 +33,14 @@ Helix uses a `config.toml` file in your `~/.config/helix` folder, so since it's ### Usage -Of course, using Helix might be weird at first glance if you are used to vim motions. +Of course, using Helix feels weird if you are used to vim motions. -It uses an _object-verb_ system : you first specify the object, then the action you want to perform on it (yank, delete, replace etc). So you might feel a bit confused with the keybinds because vim does the opposite (verb-object). You should really go checkout helix's website as it gives you everything you need to help you use their text editor. They even have a guide [for us](https://docs.helix-editor.com/from-vim.html) vim users. - -After using Helix for roughly 5 mins, I can say that I feel more comfortable **learning** Helix rather than Neovim. The Keybindings make more sense and are more intuitive. +It uses an _object-verb_ system : you first specify the object, then the action you want to perform on it (yank, delete, replace etc). So you will feel a bit confused with the keybinds because vim does the opposite (verb-object). You should really go checkout helix's website as it gives you everything you need to help you use their text editor. They even have a guide [for us](https://docs.helix-editor.com/from-vim.html) vim users. ## Conclusion +After using Helix for roughly 5 mins, I can say that I feel more comfortable **learning** Helix rather than Neovim. The Keybindings make more sense and are more intuitive. + You must have your own opinion on the subject, stop reading stupid blog posts about helix and just give it a shot :) -If you want to see my helix and neovim config here are my [dot files](https://codeberg.org/mielota/dox/src/branch/main/home/.config) +If you want to see my helix and neovim config here are my [dotfiles](https://codeberg.org/mielota/dox/src/branch/main/home/.config) |