diff options
Diffstat (limited to 'content/posts/2022-06-30-trying-out-helix-editor.md')
| -rw-r--r-- | content/posts/2022-06-30-trying-out-helix-editor.md | 53 |
1 files changed, 0 insertions, 53 deletions
diff --git a/content/posts/2022-06-30-trying-out-helix-editor.md b/content/posts/2022-06-30-trying-out-helix-editor.md deleted file mode 100644 index dc4cfed..0000000 --- a/content/posts/2022-06-30-trying-out-helix-editor.md +++ /dev/null | |||
| @@ -1,53 +0,0 @@ | |||
| 1 | --- | ||
| 2 | title: Trying out Helix code editor as my main editor | ||
| 3 | url: tying-out-helix-code-editor.html | ||
| 4 | date: 2022-06-30T12:00:00+02:00 | ||
| 5 | type: post | ||
| 6 | draft: false | ||
| 7 | --- | ||
| 8 | |||
| 9 | I have been searching for a lightweight code editor for quite some time. One of | ||
| 10 | the main reasons was that I wanted something that doesn't burn through CPU and | ||
| 11 | RAM usage is not through the roof. I have been mostly using Visual Studio Code. | ||
| 12 | It's been an outstanding editor. I have no quarrel with it at all. It's just | ||
| 13 | time to spice life up with something new. | ||
| 14 | |||
| 15 | I have been on this search for a couple of years. I have tried Vim, Neovim, | ||
| 16 | Emacs, Doom Emacs, Micro and couple more. Among most of them, I liked Micro and | ||
| 17 | Doom Emacs the most. Micro editor was a little too basic for me. And Doom Emacs | ||
| 18 | was a bit too hardcore. This does not reflect on any of the editors. It's just | ||
| 19 | my personal preference. | ||
| 20 | |||
| 21 | > I tried Helix Editor about a year ago. But I didn't pay attention to it. | ||
| 22 | > Tried it and saw it's similar to Vi and just said no. I was premature to | ||
| 23 | > dismiss it. | ||
| 24 | |||
| 25 | One of the things I actually miss is line wrapping for certain files. When | ||
| 26 | writing Markdown, line wrapping would be very helpful. Editing such a document | ||
| 27 | is frustrating to say the least. Some of the Markdown to HTML converters don't | ||
| 28 | take kindly of new lines between sentences. Not paragraphs, sentences. And I use | ||
| 29 | Markdown to write this blog you are reading. | ||
| 30 | |||
| 31 | But other than this, I have been extremely satisfied by it. It's been a pleasant | ||
| 32 | surprise. There have been zero issues with the editor. | ||
| 33 | |||
| 34 | One thing to do before you are able to use autocompletion and make use Language | ||
| 35 | Server support is to install the language server with NPM. | ||
| 36 | |||
| 37 | ```sh | ||
| 38 | npm install -g typescript typescript-language-server | ||
| 39 | ``` | ||
| 40 | |||
| 41 | I am still getting used to the keyboard shortcuts and getting better. What Helix | ||
| 42 | does really well is packing in sane defaults and even though because currently | ||
| 43 | there is no plugin support I haven't found any need for them. It has all that | ||
| 44 | you would need. It goes to extreme measures to show a user what is going on with | ||
| 45 | popups that show you what the keyboard shortcuts are. | ||
| 46 | |||
| 47 | And it comes us packed with many | ||
| 48 | [really good themes](https://github.com/helix-editor/helix/wiki/Themes). | ||
| 49 | |||
| 50 |  | ||
| 51 | |||
| 52 | It's still young but has this mature feeling to it. It has sane defaults and | ||
| 53 | mimics Vim (works a bit differently, but the overall idea is similar). | ||
