I’m leaving text editors like vscode/codium behind to learn something more modular, like Helix. I really wanna get used to. What advices can you give me to practice? I know that there is a :tutor command, I’m almost done with it. Do anyone know if there are exercices to practice? Im looking something similar to Ruby koans, a list of excersices to solve like “puzzles” but to Helix.

  • kazaika@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    6 days ago

    I’d recommend not trying to learn all the shortcuts as it’s most likely wasted effort. Most people probably dont know the entirety of available moves. Learn the basics to use the editor like, h j k l e w t f g s and start using it. Then whenever you need a ton of keystrokes to get something done, step back and see if there are moves which simplify that. Multiple selections / cursors are also an integral part of using helix so make sure to use em when applicable.

    As a sidenote helix isnt very modular imo. The appeal is that compared to e.g. neovim, it is very much a Monolith with most things you need built in which simplifies usage / configuration greatly.

    I’ll admit that this learning by doing way is prone to adopting half assed solutions but its the only way i know to get comfortable with something quickly

    • itslilith@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      0
      ·
      6 days ago

      Uhhg, I’ve been waiting for module support for helix for forever, now. It’s a planned feature, but it’s been that way for ages now

      • kazaika@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        6 days ago

        I agree that extensibility would be nice, but it cant / shouldnt replace the actually working software with all working features. Ive never been able to get into modal editors before helix because vim / neovim (probably kakoune also) are unusable in their base form by modern standards. Any actual config / distribution needs tons of work to integrate basic usability features and fall apart in a blink (and are usually not very performant - lazy loading exists for a reason). Therefore i think its the right move to focus on implementing a fully featured editor first and then explore extensibility. That said i will also be very happy when it becomes a thing, no matter if it will be via webassembly, lisp, ect…

        • itslilith@lemmy.blahaj.zone
          link
          fedilink
          arrow-up
          0
          ·
          6 days ago

          Oh I agree, I am happy with Helix and use it as my main editor already. I like that they’d rather take their time to figure out how to make plugins work well.