summaryrefslogtreecommitdiff
path: root/content/old.blog/trying-out-helix.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/old.blog/trying-out-helix.md')
-rw-r--r--content/old.blog/trying-out-helix.md44
1 files changed, 0 insertions, 44 deletions
diff --git a/content/old.blog/trying-out-helix.md b/content/old.blog/trying-out-helix.md
deleted file mode 100644
index a9e592d..0000000
--- a/content/old.blog/trying-out-helix.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-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 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
-
-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 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 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 :)