There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

natecox ,
@natecox@lemmy.sdf.org avatar

I am a fairly long time emacs user, used it as my primary editor and note taking app for around six years. I have a config large enough to warrant its own git repo separate from my normal dotfiles.

Before emacs I used vim for several years.

After really getting into Rust, I decided about three months ago to just take a look at helix and see what it was about… and I haven’t opened emacs or vim again since.

LSP and tree-sitter cover like 90% of what my old config was doing out of the box, and the kakoune inspired key bindings just felt so natural. I feel at home without the overhead of configuration paralysis.

Don’t get me wrong, helix has plenty of room to grow, but I’m excited to grow with it.

zygo_histo_morpheus ,

I sometimes play around with Helix and I almost always have a good time, but there are too many vim features that I have integrated in my workflow that there isn’t any good equivalent to in Helix. I use ex commands, the quickfix list, snippets, the fugitive plugin and just little custom commands and mappings that I’ve accumulated. I don’t see myself switching to any editor full time that doesn’t have a replacement for most of these features, but Helix is very nice and fun to use occasionally.

SubArcticTundra ,
@SubArcticTundra@lemmy.ml avatar

I’m still a fan of turbo, Nano on steroids

hunte ,

I kinda like Helix, I just don’t really know what’s the point of it. Some of the Kakoune bindings are marginally better than the vim default but any efficency I might get with it I instantly lose when trying to re-learn things or getting confused when I hop on a vim terminal on an other machine.

Kind of the same with the editor, it’s like a ‘batteries included vim’ but I can just get that with a really light vim config and not mess up my workflow.

I guess it’s might be cool if you are getting into it as your first modal editor but even then, if you want to use other stuff or need to use some different tools getting a vim extension will probably be easier than getting a Kakoune one.

nachtigall ,

I recently gave it a try after seeing dessalines recommending it. It is pretty cool but years of vim muscle memory won’t go away so easily :D

Fryboyter OP ,

In my opinion, users who already use vim are not the primary target audience of Helix. I see the target group more among users who want to switch from a “normal” editor to a modal editor. The selection → action model and the easier shortcuts probably make the switch easier for many. I personally don’t like vim at all because of the handling (purely subjective view). Helix will definitely not be my default editor but I get along much better with it than with vim or neovim.

KiranWells ,
@KiranWells@pawb.social avatar

When I first tried Helix, my main concern (that prevented me from getting too far into it) was not going from Vim to Helix, but the other way around. Vim (or sometimes vi) is a standard editor on almost any Linux machine, so if I am ever working on a server if a VM, I would need to know/use Vim keybinds. That made Vim a more useful tool for me to learn at the time, as I could use the skills both on my machine and anywhere else.

nachtigall ,

I don’t feel like this is true anymore. Many distros do not ship vi(m) anymore but only nano.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • random
  • [email protected]
  • lifeLocal
  • goranko
  • All magazines
    •