summaryrefslogtreecommitdiff
path: root/content/blog/trying-out-helix.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/blog/trying-out-helix.md')
-rw-r--r--content/blog/trying-out-helix.md46
1 files changed, 46 insertions, 0 deletions
diff --git a/content/blog/trying-out-helix.md b/content/blog/trying-out-helix.md
new file mode 100644
index 0000000..032e8aa
--- /dev/null
+++ b/content/blog/trying-out-helix.md
@@ -0,0 +1,46 @@
+---
+title: "Trying out Helix"
+date: 2025-09-22T09:08:19+02:00
+---
+
+## Intro
+
+So I recently learned about the [helix editor](https://helix-editor.com). If you try to use it you will see that Helix is similar to Vim and has the same three main editing modes.
+
+On a ton of distros it's easy to install it, on Arch you can just go:
+
+```sh
+sudo pacman -S helix
+```
+
+Normally, you use the helix binary with the `hx` command. But on Arch, you have to spell the whole `helix ` word out, so you should probably make an alias in your shell's config if it bothers you.
+
+```sh
+alias hx="helix"
+```
+
+## The actual Helix
+
+### Basic stuff
+
+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.
+
+### Conf
+
+Helix uses a `config.toml` file in your `~/.config/helix` folder, so since it's using the TOML format Helix configuration files are way more user-friendly than learning to use Neovim's init.lua
+
+### Usage
+
+Of course, using Helix might be weird at first glance 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.
+
+## Conclusion
+
+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)