• jecxjo@midwest.social
    link
    fedilink
    arrow-up
    8
    ·
    1 year ago

    What’s even more crazy is when you’ve used vim exclusively for 30 years to the point where you sit down at someone else’s computer and you try to use their editor and you are completely lost. You fumble around like you’re an elderly person who doesn’t know what a computer is, type random letters all over. You look senile.

    But then you show them on your computer how you can record a macro of your key commands and then use a regex to match different blocks of similar text and apply the same commands all at once. And because you used navigation based on words and lines rather than characters it all just works.

    • abraxas@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I think that’s true of all editors, though. I ended up on the intellij side of things, and it means I’m clueless about VSCode’s key patterns. I’ve only picked up ctrl-p so far, and keep having to remind myself “this is shift-shift in Microsoft”

      • tool@r.rosettast0ned.com
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        VSCode is what made me finally switch away from vim for anything but minor edits. It’s just too good.

        I did set up vim keybindings in it, though.

      • icydefiance@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Just to be helpful:

        • Alt+Shift+Up/Down to duplicate a line (IIRC on Linux this defaults to something more complicated and it’s dumb so I changed it to match Windows and OS X)
        • Ctrl+D to create multiple cursors
        • Ctrl+Space to open autocomplete
        • Ctrl+Period to open the little lightbulb menu that sometimes appears next to your cursor
        • Ctrl+Shift+P to search for commands, so you don’t need to remember any other shortcuts

        Honestly that’s about all of the shortcuts I use. The Ctrl+Shift+P menu will show you the keyboard shortcut next to the command, if it has one, so you can easily memorize it if you use a command often.

        • abraxas@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Totally fair. I think I’m sticking with Webstorm for at least one more year, but might someday give VSCode another try.

          Webstorm was the combobreaker that ended my 15 years of Vim.

          • sLLiK@lemmy.ml
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            The only thing that’s halted my rampant use of vim is… Neovim.

            • abraxas@lemmy.ml
              link
              fedilink
              English
              arrow-up
              2
              arrow-down
              1
              ·
              1 year ago

              I tried, so hard. Once you snort a line of a well-tuned IDE, it’s hard to decide “I’m going to learn these 30 extensions to replicate that experience in vim”.

              Flip-side, I hate vim mode IDEs, too, because it tends to collide with native IDE functionality. So I just “dream of vim” and pull it up for certain specific tasks.

      • salient_one@lemmy.villa-straylight.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        You can emulate double shift in VSC. It will be slightly different since it doesn’t automatically search actions and file names. So if you bind it to Quick Open as suggested by the link, you’ll have to put > to search actions and not files.