• Anticorp
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    4
    ·
    1 year ago

    I don’t understand why this is such a popular meme. Take 5 minutes to read about how Vim works, and you won’t have any more issues.

    • TimeSquirrel@kbin.social
      link
      fedilink
      arrow-up
      5
      arrow-down
      3
      ·
      edit-2
      1 year ago

      I shouldn’t really have to look up the instruction manual of a text editor to do a simple action like close the program. Every single other text editor I’ve ever used was intuitive enough to get started right away, going back to 1989.

      • Andrew@mander.xyz
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        If it’s not intuitive enough then don’t use it and don’t open it. You can always close with Ctrl+z and then kill it. Or close a terminal window like any other intuitive editor.

      • foyrkopp@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Well, it works well for some people.

        Once you get used to it, it can be a dang powerful tool. For people doing a lot of config-wrangling on the CLI (i.e. admins working a lot ovet SSH), overcoming the learning curve will pay dividends.

        If you’re working mostly locally and in a GUI environment environment, it’s probably not worth it - there’s a reason most devs use more specialized IDE’s.

    • BeigeAgenda@lemmy.ca
      link
      fedilink
      arrow-up
      1
      arrow-down
      2
      ·
      1 year ago

      Nowadays it’s easy when you open vim inside gnome terminal, in my old offline noob days it was like “oh shit my terminal is locked” and the way out was either Alt+F2 and then try again or Ctrl+Z; pkill %1.

      I never caught the vim bug and started with using joe and switched to nano later, I played with Emacs for some time but ended up using a GUI editor instead.