Nano has already supplanted the great EMacs and Vim as the most popular text editor of all linux distros, for though it has many omissions in functionality it scores over the older, more complete programs in two important respects. First, it is slightly simpler; and secondly it has the text “^ Exit” inscribed in highlighted text on its footer

EDIT : This sees to be going over some people’s heads. It’s a hitchiker’s guide to the galaxy reference.

The Hitchhiker’s Guide has already supplanted the great Encyclopaedia Galactica as the standard repository of all knowledge and wisdom, for though it has many omissions . . . it scores over the older, more pedestrian work in two important respects. First, it is slightly cheaper; and secondly it has the words DON’T PANIC inscribed in large friendly letters on its cover.

  • heliotrope@retrofed.com
    link
    fedilink
    English
    arrow-up
    11
    ·
    5 hours ago

    I’ve used Vim, NeoVim, Micro, mg(1), JOE, and even MS Edit (both the original DOS version and the recent Rust clone). No matter how complex and tailored I wrote my config, though, the features I actually used were included in GNU nano and/or my command shell without any of the bugs, bloat, learning curve, or slop.

    Using it as my default just makes sense.

    • Funkt4st1c@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      5 hours ago

      Nano is great for editing files. It is absolutely terrible for any amount of text processing or anything other than raw code copied from a tutorial

    • UnfortunateShort@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      6 hours ago

      It is insane how far using the same shortcuts literally everything else can get you in the world of terminal text editors and yet here we are

  • Solemarc@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    4 hours ago

    I use helix for all my developer work and nano for “I need to edit this config file buried somewhere in /usr/…”. I never remember to do Sudo -E

  • Xeno@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    10
    ·
    8 hours ago

    Sometimes I catch myself opening nano inside emacs’ term. I literally forget I’m using emacs and just do it on instinct. I once also opened emacs inside emacs’ term and I just stared at the screen in disbelief.

  • edinbruh@feddit.it
    link
    fedilink
    English
    arrow-up
    28
    ·
    edit-2
    10 hours ago

    It’s there and it’s easy. Most people don’t use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case.

    Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything… Even when I’m using SSH, because vscode supports SSH

    • scrion@lemmy.world
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      9 hours ago

      Every editor “supports” SSH, you can mount files on a remote SSH server via SSHFS.

      • edinbruh@feddit.it
        link
        fedilink
        English
        arrow-up
        8
        ·
        7 hours ago

        And instead vscode supports SSH (without quotes), you can connect to an SSH host, and it will open files and folders on the host like it does locally. And if you open the integrated terminal it will run on the remote host. And it will forward the git login agent so you can commit or push with the credentials of your local machine. And it can forward ports from the remote.

    • jaybone@lemmy.zip
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      2
      ·
      9 hours ago

      It’s kind of sad that many people don’t use the shell / terminal anymore, especially as part of their regular development flow. There’s so much scripting and so many shell commands you can use that will do things you just can’t do in vscode. And having an editor like vi immediately available is part of that flow.

      For me, vim and the shell are my primary IDE. I rarely fire up vscode. But I guess I’m getting old. Still faster than the younger devs who mainly use vscode and then struggle when they are forced to use the command line due to whatever circumstance where vscode is not available or appropriate. Kind of makes me sad. Feels like a valuable skill is being lost.

      • edinbruh@feddit.it
        link
        fedilink
        English
        arrow-up
        6
        ·
        8 hours ago

        Oh, I use the terminal a lot, it doesn’t throw me off. When I can’t have vscode (e.g. small openwrt devices) I can use vim. It’s just plain easier to use vscode for editing files when I can

    • homes@piefed.world
      link
      fedilink
      English
      arrow-up
      31
      arrow-down
      1
      ·
      edit-2
      11 hours ago

      That’s why nano gets used more than vi/vim. In the past, the majority of people using terminal text editors were geeks and developers. Now the majority of people using the terminal text editors are more often casual users who have no use for putting the time and effort to learn vi/vim, especially because they have no need for the extended functionality

      • chellomere@lemmy.world
        link
        fedilink
        arrow-up
        10
        arrow-down
        5
        ·
        9 hours ago

        I don’t get you people. Proper copy/paste support is “extended functionality”? I beg to differ. This is basic functionality.

        And no, single line copy/paste as offered by nano, or copy and paste through the terminal is not proper copy/paste.

        • esc@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          42 minutes ago

          Nano has proper copy/pate, it works identical to any text editor. Mark -> copy/cut -> paste

        • homes@piefed.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          43 minutes ago

          Sit down by the campfire my dear youngin’ and I’ll talk you tales of a terror myth called ASSEMBLY

          OOOOOooOOOOOooOOO!

          Machine language! Director memory addressing! AAAAAaaaaa!

          MWAHAHAHAHAHAHAHAHA!!!

          Computers existed before the year 2000, you silly children…

  • AgentSeven@lemmy.zip
    link
    fedilink
    arrow-up
    10
    ·
    9 hours ago

    I’m in the “been working with Linux since the 90s” gang so I call vim vi and nano pico and when I started there was a coolness factor to be considered. I was incredibly uncool so I used whatever I wanted, including pico - I mean you used pine for email back in the day and the interface was nearly identical, so whatever.

    But I did want to be at least a tiny bit cooler, so I learned vi in a fairly rudimentary fashion. I can edit, jump, delete, search, replace, copy and paste - oh, and I can exit. I’ve spent so much time using vi, that my brain doesn’t even have to think about exiting, not even whether I want to write or not. It just happens like second nature. It’s actually gotten to where nano seems unduly burdensome to me.

    But really, I prefer an IDE for programming. CLI editors will always be for configuration files and shell scripts to me.

  • Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    55
    ·
    edit-2
    13 hours ago

    Many were increasingly of the opinion that they’d all made a big mistake in making text editors in the first place. And some said that even making operating systems had been a bad move, and that no one should ever have built computers at all.

    • Skullgrid@lemmy.worldOP
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      9 hours ago

      If ind it quite funny that the majority of the posts are about the text editor and not about the blatant hitchhiker’s guide reference to the point where I had to specify it in the OP and then the thread exploded after that point.

  • perishthethought@piefed.social
    link
    fedilink
    English
    arrow-up
    10
    ·
    12 hours ago

    I’m part of the “learned Linux when I got my first raspberry pi” gang, and all Ras pi tutorials tell you to use nano. So yes.