• myrmidex@belgae.social
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      8 days ago

      Sub renewal is coming up in July. I’m seriously wondering whether I can get these vim bindings down before then.

      • JustAnotherKay@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        8 days ago

        Honestly just memorize the fundamental ones and google everything else you need on the fly. You’ll naturally memorize the ones you use often.

        I’ve used VIM for nearly 5 years and the only keybinds I have memorized are ‘a’ (append right here) ‘A’ (append to end of line) ‘i’ (insert right here) and I use the arrows to navigate instead of the letters. The only incantation I have memorized is %s/text to replace/text to replace with/g (find and replace through entire file. Remove the /g to find and replace only the next instance).

        Once you have those, you can basically do anything that you’re capable of in a normal editor. If you need to do something beyond that, search “how to x in vim” and click the first stack overflow link that comes up, hasn’t failed me yet

      • Damarus@feddit.org
        link
        fedilink
        arrow-up
        0
        ·
        8 days ago

        You can keep using the current version without renewing your license, so there is no rush

    • Ephera@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 days ago

      Lots of simpler editors gained tab completion support over the last few years, thanks to the LSP protocol. I have it in Kate, for example.

      • zwerg@feddit.org
        link
        fedilink
        arrow-up
        0
        ·
        8 days ago

        I dream of an alternate reality where everyone started using Kate instead of VSCode.

        • Ephera@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 days ago

          Yeah, to be honest, I’ve given up on that one. “Language Server Protocol” is a classic case of Microsoft naming things.
          The two differentiating words are “language” and “server”. It does not specify what kind of language is being served or what it even means to serve a language. And “server” is entirely redundant with it being a protocol. Not to mention, that “server” is the most overused word in IT and therefore virtually meaningless.
          For all we know, it could be a protocol for butlers carrying French dictionaries.

          So yeah, I use the acronym as its name, because it is similarly meaningful while being actually recognizable. And when I need to specify whether I’m talking about the “protocol named Language Server Protocol” or a “Language Server Protocol server” or even a “Language Server Protocol client”, I will just slap that behind the acronym and be done with it.

          🫠