me like use nano. nano say how do thing. nano exit easy.

  • I Cast Fist@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    2 hours ago

    Emacs is a table saw, vim is a chainsaw, nano is a scissor. Every problem those 3 solve is a differently sized single sheet of paper.

  • Francislewwis@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    3 hours ago

    Honestly nano is perfect for quick edits. Vim and Emacs are powerful, but sometimes you just want to open a config file, change one line, and exit without fighting the editor. 😄

  • Bilb!@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    3 hours ago

    Linux text editor discourse has been baffling to me for decades now. I don’t care which you use, and I care even less about why.

  • Rose@slrpnk.net
    link
    fedilink
    arrow-up
    2
    ·
    2 hours ago

    VS Code is probably the editor that’s easiest to exit. If I ran it on the computer I first ran Emacs on, it’d exit immediately, because VS Code requires a modern version of Windows and that computer had Windows 3.11. If I ran it on the first computer I ran Linux on, it’d also exit immediately because the machine would run out of memory. (…it was a 486DX, I don’t remember how much memory it had, but VS Code doesn’t run well if your memory is measured in megabytes)

  • Hemingways_Shotgun@lemmy.ca
    link
    fedilink
    English
    arrow-up
    8
    ·
    4 hours ago

    nano is usually built in. Adding another one is just redundant if all you’re using it for is editing an occasional config file.

    Honestly never understood the hate for it. Who cares? Petty, stupid, nerd-wars over little crap like a text editor is the reason average people don’t even consider linux.

    • Skullgrid@lemmy.worldOP
      link
      fedilink
      arrow-up
      5
      ·
      4 hours ago

      I very rarely see people hate nano (except a few comments in this thread), and I always see nano recommended as the text editor when people give advice on doing things in the command line

  • AnUnusualRelic@lemmy.world
    link
    fedilink
    English
    arrow-up
    7
    ·
    7 hours ago

    I first ran into nano when I gave Gentoo a try. I had to edit a few config files, so I ran vi… no vi. Emacs? No Emacs. Well, shit, what am I supposed to do? So I went back a bit and read more carefully, apparently there was a thing called nano.
    So I ran that. Ew. It was a clone of an old DOS editor of all things. What kind of lunatic had ported that? Anyway I managed to do my edits with it, added normal editors to the system and was on my way.
    It was also the last time I used it.

  • Cevilia (they/she/…)@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    30
    ·
    16 hours ago

    Fortunately, every computer comes equipped with an “exit editor” button. It’s on the back, attached to the power supply unit. You just flick the switch. Exits every editor known to humanity. /j

  • smh@slrpnk.net
    link
    fedilink
    arrow-up
    34
    ·
    21 hours ago

    I love nano. I used to do tech support for a Linux-based content management system (before SAaS take took off)… The customer sysadmins were sometimes whichever engineer was volun-told to do it, so competency varied wildly.

    I helped mostly with installs. This might be the poor newbie sysadmin’s first time on the command line. Nano was my go-to suggestion for editing config files–all the commands are right there! Much less intimidating than vi or emacs for a newbie.

  • MehBlah@lemmy.world
    link
    fedilink
    English
    arrow-up
    163
    ·
    1 day ago

    The image is misleading. The brain sizes represent the amount of grey matter it takes to operate the editor. The nano guy has plenty of brain power left over for things like hygiene, breathing and basic reasoning.

  • Grass@sh.itjust.works
    link
    fedilink
    arrow-up
    14
    ·
    19 hours ago

    I used some distro with vim back in the day and I just kept using it. I lose my shit when I use something with just nano and my muscle memory tries to do a vim thing.