142
What is something you want to use, yet are NOT using? (lemmy.ml)
submitted 2 years ago by to c/linux@lemmy.ml
180 comments fedilink hide all child comments
 

For me, I really want to get into niri, but the lack of XWayland support scares me (I know there’s solutions, but I don’t understand them yet).

Also, I stopped using Emacs (even though I love its design and philosophy with my whole heart) because it’s very slow, even as a daemon.

you are viewing a single comment's thread
view the rest of the comments
[–] 21 points 2 years ago (4 children)

I want to use Neovim but I haven't gotten around to really learning it yet.

  • permalink
  • fedilink
  • source
  • hideshow 8 child comments
    •
  • [–] 23 points 2 years ago (4 children)

    I used neovim but recently switched to helix and highly recommend it. If you haven't tried nvim yet, give helix a try before deciding. A good way to compare is do the tutorial of each and see which you like more nvim +Tutor and hx --tutor (orhelix --tutor).

    If you're a current vim user the helix keybindings are only a small learning curve after the tutorial, and feel a lot smoother imo

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 10 points 2 years ago (2 children)

    I love Helix. I like that it pretty much works out of the box and the only thing you have to do is install language servers and in some cases configure them, but that's (mostly) well documented. No need to install plugins or use a preset "distribution" like with NeoVim. I also like the built-in keyboard shortcut hints, for example when you press g (goto) it shows you what key will do what.

    The way Helix does "select first, then act" is subjective, but I like it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 2 years ago*

    Agree on all counts. I didn't like finding and comparing plugins for neovim, and then wrestling with environment stuff to get them to work, and having to change a bunch of options to get nvim to work how I want. With helix, my config of things I've changed from default is very small, and there's no wrestling with plugins.

    And yeah, "select then act" feels a lot smoother and more intuitive to me. If you like that and like plugins tho, check out kakuone

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 2 years ago

    I've used helix for a few months and liked a few default keybindings. Didn't like the reversed sequences (movement then action) so switched back to neovim and configured helix like bindings for some actions.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago (1 child)

    I tried out Helix, but I think the biggest issue that I have is that with (neo)vim, I can use the keybindings in most of the editors I use through a plugin (such as IdeaVim for the JetBrains suite) - but I do not think the concept of Helix keybinding plugins have really hit anywhere.

    Helix itself seemed really cool when I was playing around with the tutor mode though.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 2 years ago

    That's me as well, I've used vim for simple edits over the years but more and more just used nano for most of my terminal based edits. Finally ran vimtutor (mainly because I wasn't aware of it) and wow, I should have done that years ago.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 5 points 2 years ago

    NeoVim is almost a drop-in replacement for Vim (the configuration file is under .config). Plugin installation might be different, tho.

    Find a migration guide and be brave.

  • permalink
  • fedilink
  • source
  • parent