GNU Nano 6.3

by marcodiego • 4 years ago

147 109 4 years ago

fatcow• 4 years ago

So much fun in this editor. I'm surprised it is getting so much regular development. A breath of fresh air, it has helped edit many config files on remote shells.

bombcar• 4 years ago

From an editor that most people can exit to an actually powerful editor on its own right, nano has definitely evolved from just being a pico clone.

It's really nice for config file editing if color-coding is enabled and supports the config file you're working on.

waynecochran• 4 years ago

Doesn't emacs have a nano mode?

klodolph3• 4 years ago

Maybe you can get one. I don’t see a nano mode in MELPA or GNU, and it doesn’t ship with Emacs. Nano is also much more likely to be installed than Emacs, especially since Apple stopped shipping Emacs with macOS.

gnulinux2• 4 years ago

Regardless emacs can take long to boot up (unless you invoke it with -Q) but nano is instant. So when I need to change one line of a file real quick, nano is the better tool imho.

distantsounds2• 4 years ago

can't you just... use nano?

warvariuc2• 4 years ago

Since I discovered micro[1], it's my go to editor.

[1] https://micro-editor.github.io/

smoldesu• 4 years ago

Another Micro advocate! I agree, it's also my go-to editor. It's a great halfway point between breaking out Emacs and resorting to Nano. Micro is dead-simple and gets work done without any complication.

seanwilson2• 4 years ago

In Micro, selecting text using shift with left/right arrow works (across lines too), but is there a way to make it work when you press up/down arrows? And how do you shift select to the end of the line?

sph• 4 years ago

micro > nano

If it's not vim or emacs, a simple editor with CUA key binds should be the default everywhere, not nano.

I love it.

prmoustache3• 4 years ago

Is it that weird editor they tend to put on our distro these days were we end up having a lot of i x r R :s/foo/bar :w and :q embedded in the text and that we need to close quickly in fear of adding syntax error before doing an EDITOR=vi ?

______-_-______• 4 years ago

Who is "we"? You might be the only person out there who types out 7 full vim commands before opening your eyes to look at what app is running

yjftsjthsd-h2• 4 years ago

Then `export EDITOR=vi` in your profile? Or in whichever global config file in /etc is appropriate, or possibly using your distro's alternatives system? This is an extremely solvable problem.

webmobdev2• 4 years ago

I love Nano - it was the first terminal editor that I learned to use when Vi and other alternates seemed unnecessarily complex and felt masochistic (for someone who preferred a GUI for everything). (And on a hunch I just checked - Nano in macOS is still stuck at version 2.0.6!).

adamomada3• 4 years ago

From a few comments above, you may be seeing pico instead of nano on latest Mac OS

[0] https://osxdaily.com/2022/03/27/get-nano-text-editor-mac/

webmobdev2• 4 years ago

No, I am on an older version of macOS and it is GNU Nano:

$ nano --version

GNU nano version 2.0.6 (compiled 19:02:51, Feb 22 2019) Email: nano@nano-editor.org Web: http://www.nano-editor.org/ Compiled options: --disable-nls --enable-color --enable-extra --enable-multibuffer --enable-nanorc --enable-utf8

(Anyway, upgraded to the latest version from MacPorts - https://ports.macports.org/port/nano/ ).

dlandis• 4 years ago

I like nano for quick edits , but I was always bemused that it only gained an undo feature around the mid 2010s despite existing for many years before that.

lakomen• 4 years ago

My first shared hosting provider used some BSD, I don't remember which. It was way back in the early 2000s. I could log in via ssh. But at home I used Gentoo and I couldn't deal with the remote shell at first. I had to press scroll lock to scroll up and down, found it out by accident. I asked the hoster how to edit files. He said Pico ctrl+o ctrl+x to save and exit. Pico then became my editor, because vi was even more alien. I believe everyone has searched for "how to quit vi" once :) . Anyhow, I wanted Pico at home and found that it didn't either exist for Linux or wasn't maintained anymore. And that there was this nano thing now. And to this day I use "nano -w" to edit files remotely and sometimes even locally.

bobochan• 4 years ago

I had a similar path to nano. Pico was the default editor for the Pine email client, and I still use Alpine for work decades later. I am generally an emacs user, but nano / pico definitely feel familiar and comfortable.

cf100clunk• 4 years ago

Same background for me and I'm quite literate with vi and emacs if/as needed, so now Alpine (email client) and nano are one-for-one replacements.

Decabytes• 4 years ago

As an Emacs user I never really understood why Nano was so popular when you could use Emacs, but I've since learned a few things...

1. Emacs isn't always on all the systems, and getting it downloaded/setup can be a pain in the butt

2. Sometimes it's just easier to launch nano quickly to edit one line in a .bashrc from the command line

3. When I bork Emacs and it doesn't work, it's nice to be able to fall back on a simple editor to edit my .emacs.d

4. It's nice to have an alternative to vi with keybindings I'm more familiar with

eixiepia• 4 years ago

5. Sometimes you don't need an operating system, but a decent editor and that's where Nano come in :)

zdkl• 4 years ago

I never really understood why Nano was so popular when you could use Emacs
When I bork Emacs and it doesn't work

Only 50 % joking but like you said it's not if, it's when. Nano is there and works.

avgcorrection• 4 years ago

`emacs --quick`?

anthk4• 4 years ago

emacs -q

NelsonMinar3• 4 years ago

Back in the 90s the joke was "Eight Megabytes And Constantly Swapping". 8mb is nothing now and I note that Nano, with no file open, is 6768kb virtual and 3620kb resident on my x86_64 Linux box.

(I use mg as my small emacs alternative; full emacs UI but tiny binary / memory. Unfortunately it doesn't support Unicode properly.)

anthk4• 4 years ago

Check jmacs from joe.

xxpor• 4 years ago

I wonder how much of the base data structures that are always in memory are pointers, and if it'd be more fair to say it's really the equivalent of 3 mb virtual/1.5 mb resident (or even 1.5/.75 for 16 bit!)

soraminazuki4• 4 years ago

Modern operating systems and memory allocation techniques make it hard to account for memory usage in a meaningful manner without a more in-depth investigation of program behavior. Quick stats from memory reporting tools aren't worth much in isolation unless those numbers significantly deviate from expectations.

distantsounds2• 4 years ago

Nano is _by far_ easier to use as a first-timer on the command line. Emacs is an amalgamation of a scripting language that happens to have a text editor built in.

newswasboring2• 4 years ago

Honestly the main reason seems to be that it looks less intimidating. Open vi and no help is offered in terms of commands, it's just an empty screen. Same for Emacs i think. Nano looks like something built for humans.

soraminazuki4• 4 years ago

This is the greeting text that is displayed when you launch Vim [1]:

    VIM - Vi IMproved
    
    version 8.2.4133
    by Bram Moolenaar et al.
    
    Vim is open source and freely distributable
    
    Help poor children in Uganda!
    type  :help iccf<Enter>       for information 
    
    type  :q<Enter>               to exit         
    type  :help<Enter>  or  <F1>  for on-line help
    type  :help version8<Enter>   for version info
    
    Running in Vi compatible mode
    type  :set nocp<Enter>        for Vim defaults
    type  :help cp-default<Enter> for info on this

"No help offered" or "just an empty screen" is not how I would describe the above text.

[1] https://github.com/vim/vim/blob/a96edb736d4274fc4aea46080078...

bc4m• 4 years ago

The Emacs welcome screen links to a tutorial, a guided tour, and manual, all of which are inside Emacs. I would say its help functionality is potentially its greatest strength.

yaantc• 4 years ago

I used to use jed instead of nano for quick edits, but same idea really. Then one day I realized that "emacs -nw -Q" starts subjectively instantly, and is also immune to a borked configuration ("-Q" skips it). So I just created a short alias for it and use it. Bonus: one can always load all the configuration later if needed.

That doesn't solve point 1 obviously, but then that's never been an issue for me: emacs is always where I need it, and then there's always TRAMP.

codedokode• 4 years ago

I use nano when I need to edit something from CLI because I don't like ancient editors with modes or non-standard key combinations from 80s. And in nano the most important shortcuts are at least written in the bottom of screen.

While nano supports some standard shortcuts (arrows, Ctrl + arrows, Home, End, PgUp, PgDn), others are non-standard and I don't understand why. For example, "save" is Ctrl + O instead of common Ctrl + S, exit is "Ctrl + X" instead of "Ctrl + Q", Esc doesn't work when you want to cancel search, and so on. What a nonsense. Why should someone use different shortcuts for the same function.

klyrs• 4 years ago

This made me chuckle. Pico was the first non-BASIC editor I used because the public library BBS used Pine. As a descendant of Pico, I'd say that Nano is an ancient editor, and it comes with all the historical baggage fueling your complaints.

soraminazuki4• 4 years ago

It's not a good idea to use Ctrl + s and Ctrl + q as default keybindings for any important functionality on the terminal because terminals traditionally used them to stop/resume terminal output. Some terminal emulators still do this, so making people press those keys unwittingly would be problematic. So no, nano developers aren't being non-sensical here.

gnubison3• 4 years ago

Actually, ^S does save, since 2017.

brimble• 4 years ago

An editor with always-on help displaying the most common actions one might want to perform, is super-useful not just for n00bs, but for anyone who doesn't work on the command line enough to memorize the commands to operate vim and emacs.

Crucially, you don't have to ask nano for help. It helps by default.

throwawayboise• 4 years ago

Emacs isn't always on all the systems

Nor is nano.

vi is about the only editor that can be assumed to be available on a unix-like system.

progre• 4 years ago

Ed is the standard editor

politelemon• 4 years ago

I was introduced to nano when I did a `crontab -e` for the first time, and it had an ASCII arrow pointing at nano, saying 'easiest'. I tried it and realized it was perfect for quickly editing a file and getting out. I use it when guiding people unfamiliar with the CLI and they seem more comfortable with its shortcuts, as opposed to vi.

My Ubuntu is a bit behind, is this the official PPA for nano, or good enough? https://launchpad.net/ubuntu/+source/nano

jjice• 4 years ago

Nano helped me edit config files on a Raspberry Pi when I was 15 - very grateful for it for those moment. I use vim for remote editing and notes now as I've gotten familiar and prefer it, but Nano absolutely has it's place.

Lambdanaut• 4 years ago

In high school I'd have to wait a few hours in the library every evening to be picked up, so I set up an SSH server at home and had my laptop with me. I didn't know about GIT at that time, so I'd SSH into my home server and edit files on the fly with Nano.

I actually coded quite a bit, and built a basic social networking app fully in nano.

Looking back I have no idea how I did it. Anything less than an IDE with VIM-mode is a no-go for me these days.

freedomben• 4 years ago

tldr: Main focus this release is on performance/optimization.

Multiline regexes, and colorization improvements (including NO_COLOR env var to disable). Support added for xsel (although it seems like most distros aren't using x anymore but better late than never!).

marcodiego• 4 years ago

The fact is not that it now supports "xsel", the fact is a bug was fixed that prevented its usage.

cosmiccatnap• 4 years ago

I wish back in the day people coming from windows were shown nano/pico instead of vi. If they had known there was something very analogous to dos edit I would think more windows people wouldn't have the experience with Unix they seem to have had.

Even today I am not a vim purist. I tell people to try nano out at first and work their way up to emacs or vim cause in the real world most people are just changing a line in etc that broke something.

latchkey• 4 years ago

I do an Ubuntu based PXE deployment to over 10k servers. I still put nano on there.

ndm000• 4 years ago

I am teaching my 10 year old Python using Nano, and he’s picked it up surprisingly quickly. When I wanted him to upgrade to VS Code, he preferred the terminal! Nano’s a great product, thanks for the hard work on it all.

teaearlgraycold• 4 years ago

Sounds great. Starting small makes sense. I wrote my first code in MS Notepad. Then used Notepad++. I use VS Code these days but can’t see what it would have done for me as a child.

shortlived• 4 years ago

Give me Vi or give me death!

JK - glad to see Nano is still being developed. It was my first editor on Linux before I could learn Vi/m.

blippage• 4 years ago

Give me Vi or give me death!

When I was doing my PhD back in the 90's, I was mostly using Windows 3.11 and writing in Fortran. My editor: Notepad. Seems incredible now. The big boys doing other research had Unix boxes, big expensive Silicon Graphics machines of various colours, I believe. One of the programmers explained to me that vi was an excellent editor, and how you used h,j,k,l to move around. I kinda rolled my eyes and thought he was mad.

A systems programmer also suggested that I used "make". I couldn't understand the point of that, as that was what batch files were for.

Roll on to the present day, and vim is my editor of choice. I did flirt with emacs at one point, but gave it up as too much configuration is involved. On vim, I do virtually no configuration. I have no plugins whatsoever, although I have set up a few custom bits and pieces in .vimrc. With just one file, it makes it very easy to bring up a new machine for me.

I've come to the conclusion that emacs and vim are very different philosophies. With emacs, it works the way you want. With vim, you work they way vim wants. So ditch your plugins, and use vim the way nature intended.

Before doing my PhD, I did a masters jointly split between two universities. I think you can tell a lot about universities by what computer systems they have. One university had a lot of Sun systems. The file servers were prone to the odd hiccup, mind. At the other university, it was mostly Windows systems. In order to program in Fortran, we had to log into the university's computer (it was some Unix system, although I don't know specifics) via telnet, or something. And use "ed". Boy, was there some bellyaching from the students over that one! I always preferred the university with the proper Unix workstations. The Windows ones always seemed a bit of a joke, without proper software like Maple (IIRC).

JCWasmx86• 4 years ago

nano is the first thing I always install on a fresh install (If it is not already preinstalled)

mrweasel• 4 years ago

One of my former co-workers loves Nano. It does what he needs, it was installed on all our systems, if not it is safe to just apt-get install it. Most of our documentation said this like "edit this line in this file, using: vi <path to file>." Every time he wrote documentation, or updated existing, he'd change "vi" to "nano".

It always makes me smile and think about him when I spot "nano" somewhere in the documentation.

rob742• 4 years ago

Nano's great advantage over vi(m) is that you can instantly see how you can save the current file and exit the editor, e.g. when confronted with it because of a "git commit" on some server. So, if you configure an editor that anyone should be able to use, I would prefer Nano too...

cesarb3• 4 years ago

Every time he wrote documentation, or updated existing, he'd change "vi" to "nano".

It might be better to change it to "nano -w" instead; IIRC, some versions of nano hard-wrap lines by default (which corrupts files where line breaks are significant) unless you remember to always use "nano -w".

juangacovas• 4 years ago

You can add a "set nowrap" line into your home ".nanorc" file so "-w" is applied by default.

pachico• 4 years ago

Since I was a little kid my nickname was Nano.

One day I found an editor named Nano and I've been using it since :)

cjohansson• 4 years ago

Nano is great, when I did not know how to use vi, vim or emacs I used nano. Nowdays for quick edits in terminal on unexplored servers I use vi. emacs and vim are not always installed

rob742• 4 years ago

Interesting codenames, very cosmopolitan (if a bit cryptic). I can translate the Romanian ones:

v6.1: "Social networks are like a fridge"

v5.7: "All the others were plowing the fields"

rgovostes• 4 years ago

Apple was shipping nano 2.0.6—from 2007!—until the current mid-cycle release, macOS 12.3. Probably due to newer releases of nano being GPLv3, they quietly replaced it with pico, which unfortunately lacks the critical Go To Line (^-) function.

rurban• 4 years ago

I recently switched from joe to nano on small remote boxes, because it's there.

I'm still having issues to move lines around. Cannot get rid of my 80ies habits of C-k b, C-k e

GNU Nano 6.3

Related Stories