• chicken@lemmy.dbzer0.com
      2·
      5 months ago

      The good thing about nano is that it has clear instructions for how to close it right there immediately in front of you

      • esc27@lemmy.world
        2·
        5 months ago

        Not if aren’t familiar with control characters. Might was well be three seashells…

        • laurelraven@lemmy.blahaj.zone
          1·
          5 months ago

          Same, every new system that defaults to nano and throws me in here when I’m expecting vim I have to stop and remember what the characters mean right before changing it to use vim (like, seriously, I typed “visudo”, not “nanosudo”, why the hell would I expect it to open in anything other than vi or vim?)

    • loo@lemmy.worldEnglish
      1·
      5 months ago

      I’ve always been using nano, but since I refused to ever read the docs, I’m still confused

  • rtxn@lemmy.worldMEnglish
    0·
    5 months ago

    From the torrent, the deluge, the unending tidal wave of this exact meme in various formats. The “exit vim difficult” meme must constitute at least 50% of online content regarding *nix and *nix-adjacent systems. It is so stale that Slackware considers it outdated. It is the “mayonnaise is spicy” equivalent of funny. It is the white bread, picket fence stereotype of meme culture, yes offense. I’d like to say that it’s beating a dead horse, but the horse is gone; its flesh has been tenderized, pulverized, and evaporated from the sum total of energy imparted by the constant beating. If the heat death of the universe were to happen tomorrow, and from the uniform vacuum energy a Boltzmann brain were to spontaneously form, it will have been already tired of this meme.

    But to answer the question, it was either that, or the big

    type :q<Enter> to exit

    splash that appears when I open it with an empty buffer, and following its instructions.

    No offense to you or your house, but I’m really tired of this meme.

    • uranibaba@lemmy.world
      1·
      5 months ago

      splash that appears when I open it with an empty buffer, and following its instructions.

      That’s the key to the problem, I have almost never open vim with an empty buffer, almost only used it to open files directly. Since there is no nice splash screen telling you how to exit when you use vi <your_file>, this meme happens.