Some of my favorite memories are of learning C++ using the nano editor. I ended up a C# dev, put I still put nano on all my Windows boxes. It can be quite handy.
GNU nano 2.9.0
31–40 of 62 posts
Re: GNU nano 2.9.0
#32I used nano for years until I was forced to use vi when I was doing a FreeBSD install just for fun on my Cr-48. Once vim clicked for me I never went back. At the same time, Nano was invaluable as an easy to use terminal editor as a beginner. It was a huge help when I was learning to use Linux.
Re: GNU nano 2.9.0
#33So I was looking through the sources of nano and I seemed to have discovered a previously-unknown (at least based on a quick search) easter egg. First modify the buffer somehow. It really doesn't matter if you just type in "test" Hit ^X to exit nano. When it asks you if you want to save the buffer hit Y Save the file as "zzy" and press ENTER to trigger the Easter egg ^X+Y+zzy is likely a reference to xyzzy, a cheat c…
'xyzzy' was also what enabled cheat-mode in Road Rash[1]. Ah.. good 'ol days..
Re: GNU nano 2.9.0
#34Earlier quoted context omitted.
Every time I'm sysadminning some Linux server or another. It's everywhere and does the job well enough without me having to learn vim :-D I also often use it to look inside random files on my Mac that won't open anywhere else (e.g. .xml, .json, files without extension names).
I think vi is probably more ubiquitous though, especially since it’s included in busybox which powers almost all imbedded Linux hosts. Still a good idea to learn a little vim
>I think vi is probably more ubiquitous though,
As I mentioned below, While it may be more ubiquitous, vi isn't present on Debian's live cd, while nano is.
Re: GNU nano 2.9.0
#35Is anyone using this thing?
Yes. It's great for avoiding vi.
Re: GNU nano 2.9.0
#36I used nano for years until I was forced to use vi when I was doing a FreeBSD install just for fun on my Cr-48. Once vim clicked for me I never went back. At the same time, Nano was invaluable as an easy to use terminal editor as a beginner. It was a huge help when I was learning to use Linux.
It's weird how comfortable familiarity is. I approached vim similarly, I first used pico/nano to modify files here and there but mostly used GUI IDEs or editors. Switched to vim and been using it for 10+ years.
Every once in awhile I encounter an OS where visudo or something else defaults to nano and I feel so awkward just trying to make simple changes and save the file.
Re: GNU nano 2.9.0
#37I used nano for years until I was forced to use vi when I was doing a FreeBSD install just for fun on my Cr-48. Once vim clicked for me I never went back. At the same time, Nano was invaluable as an easy to use terminal editor as a beginner. It was a huge help when I was learning to use Linux.
It's weird how comfortable familiarity is. I approached vim similarly, I first used pico/nano to modify files here and there but mostly used GUI IDEs or editors. Switched to vim and been using it for 10+ years. Every once in awhile I encounter an OS where visudo or something else defaults to nano and I feel so awkward just trying to make simple changes and save the file.
If vim is available, then you can do
VISUAL=vim visudo
EDITOR=vim visudo
Re: GNU nano 2.9.0
#38echo "export EDITOR=nano" >> ~/.bashrc
sed -i s,^EDITOR=nano$,EDITOR=vim ~/.bashrcRe: GNU nano 2.9.0
#39I used nano for years until I was forced to use vi when I was doing a FreeBSD install just for fun on my Cr-48. Once vim clicked for me I never went back. At the same time, Nano was invaluable as an easy to use terminal editor as a beginner. It was a huge help when I was learning to use Linux.
It's weird how comfortable familiarity is. I approached vim similarly, I first used pico/nano to modify files here and there but mostly used GUI IDEs or editors. Switched to vim and been using it for 10+ years. Every once in awhile I encounter an OS where visudo or something else defaults to nano and I feel so awkward just trying to make simple changes and save the file.
The huge advantage of nano over vi in that scenario, is that nano 1) uses the conventional [i.e. as used by every editor other than vi] arrow key cursor movement and typing behavior without the need to toggle any modes etc, and 2) displays the shortcuts you need for anything else on the screen by default - things like saving, cutting/pasting, searching, and, oh yes, quitting.
So, while it might not be optimal for vi users, it is at least accessible to pretty much everyone regardless of their background. Whereas for someone not familiar to vi, getting thrown into the dreaded : prompt can be a frustrating nightmare.
Re: GNU nano 2.9.0
#40As a beginner it was my editor of choice, as most of us it seems. But the GUI made me want a better editor, with the same capabilities of a GUI editor.
So, when i heard of micro i switched immediately, I just find the default copy/cut/paste and the mouse functionalities very comfortable.