First time when you ssh into your Linux terminal and you gotta “sudo crontab -e” or something and it’s like “what editor do you want to use?” and nano sounds lame so you choose vim cause the sound is cool when you say it and then you have to wipe the whole comp and start over

  • Sanyanov@lemmy.world
    link
    fedilink
    arrow-up
    7
    ·
    10 months ago

    Unless you’re a sysadmin who deals with very obscure systems, you’ll always have access to nano, so why bother?

    Vim elitists love to brag about how cool Vim is, but pretty much never properly elaborate. Why should I learn all those obscure commands to just edit some text? What’s the point?

    • Jumuta@sh.itjust.works
      link
      fedilink
      arrow-up
      7
      ·
      10 months ago

      it feels smooth
      the movement is very fast and precise
      you don’t need to move your hand for arrow keys so it’s nice when you’re lazy
      i dont use vim anymore though, i use helix because it’s purple

    • Pipoca@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      Even not being a vim wizard, editing code without vim keybindings feels… slow.

      Yeah, I could grab the mouse, highlight everything between the arguments to a function and hit delete. Or I could just go to the open paren and just hit d%. I could grab the mouse, highlight the line and hit delete, or I could literally just type dd.

      And trying to edit things in nano is positively masochistic.

      • Sanyanov@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        10 months ago

        Why would someone edit the actual code (not configs) from the terminal? That by itself sounds like a masochistic endeavor. But I might be missing something.

        • Pipoca@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          edit-2
          10 months ago

          I used to do it more back in college where I’d ssh into the schools computers to work on assignments. It’s still sometimes useful if you’re in the console and want to edit something quickly.

          However, there’s e.g. macvim and gvim which are literally just vim in a gui; they give you menus and the ability to drag panes and click to move your cursor. With a decent LSP setup they can actually be pretty nice.

          And most other decent editors have vim emulation of various quality levels. Emacs is a bit buggy, but it’s really useful if you want to code in agda or clojure. And VS Code has fairly decent vim emulation.

    • thews@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      10 months ago

      I learned them and basically never use vim.

      I use sed if i need to change things with a pattern, cat the file if i need to see the contents, use head or tail if its too much to fit on the screen.

      If I am writing code, I use a code editor. Emacs and vim can do a lot, but they can also fuck off.