Nano is extremely valuable for people learning the system. Typical alternatives are vi and emacs, which are extremely opaque, to the point that it's not even obvious how to exit them. UNIX tutorials will often say "use control-C to kill a command" and then that doesn't even work for this!
Nano tells you how to use it right on the screen. Control-C still doesn't work, but it tells you how to exit. Saving files, paging, cut and paste commands are all shown. There's easily accessible help!
If you're learning UNIX then editing files is handy. Without nano, you'd have to spend a bunch of time learning how to use a text editor before you could do anything that needs text editing.
Not as arcane as vim, great for small edits without the oh-crap-what-have-I-pressed-force-quit-start-over phenomenon that I get in vi. 'Serious' editing is done in gedit...
vi makes me angry. This was obvious when I installed Debian on a 1999-era iMac and had to edit (probably) x11 conf and had to use vi with JKL; instead of the arrow keys. It made me want to stab something.
That's probably what they were. I was trying to remember exactly, since that was over 6 years ago, and I've never had to use vi like that before or since.
I recall many frustrating days in college when I first learned vim but not enough to configure it (or was to lazy to). The arrow keys inserted control characters in edit mode on the basic Linux install I had at the time and on the school's computers (circa 2000-2004). It was annoying. It turned me off to vim for a while, but emacs and I were a better fit anyways.
Yeah, maybe I'm just weird, but modal editing is kind of a pain unless you do it every day. It's just a little too arcane for making a quick edit to a file in /etc. It's probably even more natural for me having grown up in the shadow of the University of Washington, so PINE was the popular email client and PICO was it's editor.
Don't get me wrong, I've watched Vim power users do amazing things in that editor but those people are not me and I can't find a good reason to climb that particular mountain.
It's nice to have on boot disks, small enough to fit alongside busybox which ships with a lite vi[1] that some don't care for.
I personally love vi and am a bit taken aback sometimes when visudo pulls up nano instead of vi because I haven't installed it or made it my default editor yet.
So I'm not sure this means much to me personally but I'm always sad to see members of the community part ways. Still, I wish them all the luck and thank them for their efforts.
Back in the 1990s thru early 2000s, I used to use pico before I became comfortable with vi. For someone coming from a DOS/Windows/OS/2 background originally, it was less of a learning curve. I never used nano much, but I imagine the same reasons might apply for some people today.
(I also used to use emacs a lot, I first used it on OS/2 under EMX, but there were systems on which pico was installed but emacs wasn't. Nowadays, I'm so used to vim, I start emacs and can't remember most of the keystrokes. Oh, and the first ever email client I used was Pine.)
It fills a real need as the console-based text editor for people who don't know vi (and would usually use e.g. gedit rather than emacs).
(I'm sure it has other purposes too, but it's the most motivating one I know.)
Ubuntu X11 stopped working? Or perhaps you need to tweak the nginx config on that tiny VPS you're renting? If you don't know vim, nano is something that's very easy to use and often pre-installed.
7 years after getting into Linux, I still prefer Nano to make fast edits to text files. Coming from a Windows history shortcut keys are fairly natural to me, and although I disagree with some of the mnemonics, I've got the improtant ones memorised. There's enough features to even do light coding in it (syntax highlighting, auto-indenting etc.). Basically, I can pull up, edit and save a file before vim has even entered Insert mode.
Don't get me wrong, I understand the need for a feature-complex editor like vim, but I have never, ever gotten on with it.
I use it, as a terminal editor, whenever I can. On my machines I use it instead of vi(m), and if I have control over a remote machine, there as well, I only use VI if a server doesn't have nano and I can't install it.
yep. Beeing a DevOps since many years and still use nano for quick edits on ssh because I don't use vi(m) anywhere. Why should I learn a new editor which behaves totally different when I can use nano which behaves quite similar to my existing tools. And as you say it's on nearly every distro. On emergency I still know how to use vi... but that does not mean I like it very much.
Yes, it's much easier to work with than modal editors which I find clumsy and terrible. I don't use it intensively, just when I need to edit something quickly, usually in an SSH session.
On some distros nano is the default editor for crontab. I run into it when I ssh to servers and have to setup cronjobs. I set EDITOR=vim if it's already installed there or I keep using nano and look at the help at the bottom of the page every single time I use it. I use emacs for editing code on my computer. It has got a different set of ctrl-* and I can't remember nano's ones.
I would go straight to vim and type: "/section_start<cr>", which navigates straight to that line. Then navigate to the line, "i" to enter insert mode, make edits, and "<esc>:wq<cr>".
It is absolutely a learning curve, but the power of vim is insane. "dd" deletes lines, "A" appends to the end, "I" inserts at the beginning, "<lineno>G" jumps to a line number, all little tweaks that I use nearly every day in editing files quickly. It's especially nice when editing known_hosts where it tells you the line of the offending key, just "<line#>Gdd:wq" and it's done.
I seldom used it a long time ago, before learning the basics of vi(m). It's great when you need to change some random config and you need a commandline editor that has the basic commands listed in plain sight all the time.
I use it on some dev servers I can't install software on as an alternative to vi. Otherwise I use emacs+tramp to edit files remotely. It's not a huge use case or most of my editing. Anything to avoid vi though.
If you just have a handful of servers you can still get a lot done with the free edition, not useless at all by any stretch of the imagination. Paying a few quid a year to keep up with the updates is peanuts compared to the extra productivity we get from it.
Sounds like VT emulation settings in PuTTY might be wrong. There's nothing in vim that PuTTY doesn't support - in fact I've used vim over PuTTY many times.
