Live data from Hacker News

Helix: Post-Modern Text Editor

helix-editor.com

111–120 of 169 posts

Re: Helix: Post-Modern Text Editor

#111
Huge thank you to the helix team and contributors.

Running `hx` for the first time is one of those experiences where you go simply go, "woah". I've since never looked back and it's slowly defeating how often I open up even larger things in VS Code.

The thing that always held me back from learning `[n]vim` was the huge amount of configuration variability between all the variants and the lack of instruction on just doing something out of default. Neovim is basically the best experience out of the box but even sometimes there you want to have extra functionality. It's really hard to beat the amazing defaults in `hx` and even better `hx -g fetch||build`.

The one thing I'm still missing is ease of running singular test cases or test groups in larger codebases. This still feels hard on Helix.

Re: Helix: Post-Modern Text Editor

#112

Helix is cool if you want a terminal editor. For a GUI editor, I am very interested in https://lapce.dev/ It is perhaps the only editor which for me seems as snappy as Sublime Text.

Lite XL (lite-xl.com) is also extremely fast. Also, because a lot of it is written in Lua, you can very easily extend it yourself; you can just monkey-patch many functions and do what you want!

It's kind of immature in some ways, for example, the current release version has some limitations in the native plugin interface (which you need for loading C libraries for Lua, as Lite may use a statically linked version), and there is a conflict between the linewrapping and projectsearch plugins where opening a file from it is bugged if you have linewrapping enabled by default.

Lapce does seem more advanced in some ways, but IMO the enormous hackability of Lite is also a nice advantage.

Re: Helix: Post-Modern Text Editor

#113

Earlier quoted context omitted.

Doom Emacs looks like modern Emacs.

Not a fan to be honest. I stick with vanilla so when it breaks I can read the manual. Although I know Doom works great and makes a lot of people happy, it doesn’t do anything you can’t do yourself by downloading packages and configuring them to your needs.

That is true. But it’s pretty overwhelming for a lot of folks. I was a spacemacs user. I tried to rebuild what I liked about it. It was a lot, and I didn’t quite get it there.

I finally found a good compromise though. I started over with this confing: https://github.com/susam/emfy

From there, I only needed a handful of packages and a few dozen lines of config to get to an editor that was comfy.

Re: Helix: Post-Modern Text Editor

#118
post #85
post #20

For anyone who's used to fd/jk/kj/jj/jf or the like in Vim as an alias to ESC to exit insert mode, it looks like Helix is not too usable as of today: https://github.com/helix-editor/helix/issues/2612 I would've considered exploring Helix myself if it wasn't for this.

I use jj and jk to escape insert mode just fine...

I have the same, but it was difficult writing that essay about Dijkstra playing Blackjack in Reykjavik.

Re: Helix: Post-Modern Text Editor

#119
Am I the only one that doesn't have any strong preference for some editor?

I am always super impressed by all the comments stating how much of a night/day difference editors make to them.

I have to say that I have tried many (VSC, neovim, Emacs and Spacemacs mostly) in the last five years but at the end of the day I feel like none makes such a difference to me so I just default to whatever my colleagues use to make collaboration (fixing ide issuesm, exchanging configs and tips) easier.

Post reply on HN