Cult?
Nano is not cult.
Now vi v emacs let battle commence!
Cult text editor GNU Nano has released a major update, taking the terminal-based program to its fifth version in twenty years. The new update, called "Among the fields of barely", introduces a new --indicator command-line switch that will enable the display a kind of scrollbar on the right-hand side of the screen to indicate …
This post has been deleted by its author
There is a difference between "user friendly" and "beginner friendly" "Vi", "Vim" and "Emacs" are definitely user friendly, nano is definitely beginner friendly (haven't used it enough to know if it is also user friendly)
"Vi" probably can't be described as "beginner friendly" :-)
"learning curves" are overrated. I just wanna get those 1 minute tasks over with, not spend an hour learning how to do a "1 minutes' worth" of work, and unnecessary additional time looking up how to do otherwise-simple things in documentation EVERY! STINKING! TIME! because "I never use that hideous thing unless there is no other choice" etc..
This is why nano, and its possible predecessor 'ee', exist. Not for n00bs, per se, but for people like me who don't want to "look it up" all of the time, wasting effort that could be spent doing things that are more fun, more interesting, or maybe even just more important.
seems all of the Debian-based distros have nano - they used to include 'ee' but for some reason it's not now (abandoned?). FreeBSD still has 'ee' though.
I'm not a fan of 'vi' but I know the handful of commands that let me use it. Or more more importantly, exit without a reboot (or 'killall' from another console/session). Never type 'edit' in a console unless you're prepared for it. Did that the first time I booted a POSIX system (FreeBSD 4.7 in this case). Frustration ensued, followed by the boot button. i was still figuring it all out.
Nano seems to be most useful on an RPi when you have to ssh in a lot and edit things. I'm glad it's there. That probably makes those who use it members of a pretty big 'Cult'.
Cult as in, "Liked by relatively few but very much."
Alternatively, how about mcedit? In common with nano it shuns that Dark Cave UI style, but also has drop down menus like a sensible program. Shame it's such a faff to fix the lowest common denominator colour scheme really.
Is midnight commander and mcedit still maintained?
I wonder how much more participation Nano and other GNU projects would be if they moved to a more friendly source code manager or bug tracker rather than Savannah. Maybe it is a generational thing, but I find making a branch and then a pull request far simpler than trying to submit patches. I got into a right mess the first patch I sent to KDE (phabricator not savannah, but similar interface) when I was asked for a changes and sent a second patch to the fist patch (apparently not Kosher), finally got something through and someone else applied the patch and so I am not even in the Git history :(
I am not suggesting GitHub. I assume they have an issue with GitLab CE (which Gnome have moved to and KDE are starting to)? A Gitea clone?
That and the difficulty inherent in the copyright assignment process which many (but not all) GNU projects require. It's an ongoing discussion that raises itself every few years, and I suspect will eventually happen. Savannah is an a fork of sourceforge I think, and given that everyone has abandoned that is indicative.
Ah yes,
Nano and Pico. I tried them but could not get on with either.
What I did find and use to this day is a little extra bundled with MC called mcedit. It's all I need for editing .cfg files etc. and the key bindings are the same as MC so I found it easy to use.
It may not be for everyone but it is a little hidden gem which no-one seems to know about.
I keep nano around for simple edits, but I've compiled it myself to switch the key labels from ^G ^X ^O etc. to F1, F2, F3 etc. (Both combinations still work identically.)
It seems typical of the GNU mindset to think "Ah! But the user may be using a machine without function keys!" It's 2020.
No function keys is getting more common in 2020 rather than less so.
OK that's mostly laptops with the function keys locked into being media controls and you can usually change it but it does make some of the keyboard twister key combo presses even worse if you've got to add a "fn" key into the mix.
It seems typical of the GNU mindset to think "Ah! But the user may be using a machine without function keys!" It's 2020.
Personally I find function keys just a little too far away from my fingers, and I can't find them without looking (but I guess that's at least partly because I don't use them much). So perhaps "machine without function keys" is not the reason, or at least not the only reason.
the only complaint I have about nano is if the Linux distro (say, Raspbian) set up HIDEOUS colorization and I'm trying to edit a file and it's dark grey on black and I can't freaking READ it...
That's editable, fortunately, once you've found out where it is. But I'd like a switch or ~/.something setting to turn it OFF, like I do when I 'unalias ls' and things like that. Colorized text on black background NEVER looks right. It should be easy to turn it ALL off without mucking with 'term' settings in .profile or .bashrc or elsewhere.
color choices aren't just for "I like" vs "I hate". My ~60 year old eyes need less strain, and so I minimize that with off-white backgrounds in the GUI, and white-on-black consoles. Turning off hidesouly dim colors on black background (favoring NO colors) would be a nice start, especially if it's just a single line in a config file, or something I can 'alias'... or 'unalias' as the case may be.
Colourised text on a light background is also useless. Many common colours in the typical ls -c setup leave you with unreadable filenames.
I always assumed this was because 1334 distro releasers liked dark screens to go with their hoodies, so it's interesting that you find them rubbish on dark, too.
Where do these idiot colour choices come from and why are they default ? GUI applications don't seem to have this problem (ignoring 'cool' websites) but consoles can't seem to get it right.
Is the problem that it's configurable, and therefore MUST be configured - even if it doesn't help ?
OMG I just agreed with bb. Igmc..
I've just discovered the editor ...
Arriving in the Linux camp after 20+ years of MS OSs (DOS onwards) I had a hard time struggling with the usual recommended editors (and their variety) till I came across 'jed'.
That's what I use these days with the ocasional fling with mcedit, but then I am not a coder/programmer.
O.
Actually I thought the QBasic editor was pretty good, too. Almost too late the party, though. By the time MS-DOS had a decent editor, Windows 3.0 released.
Many of those old MS-DOS edit things (especially for programmers, like Turbo C's editor, PWB, and QBasic) seem to be EMACS-like in a lot of ways.
Though I hve to admit I prefer 'ee' to 'nano'. As I recall, 'ee' used libcurses, and I wonder if that has something to do with why the debian-based distros don't seem to have it any more... (everything else seems to use libncurses now, and FreeBSD's base has a 'new_curses.c' that implements curses for 'ee' in the contributed source tree - and the BSD license possibly keeps it out of certain Linux distros).
edlin evil? Edlin was simplicity itself...at least for a line editor.
I've used a lot of line editors on a lot of old, obscure systems, and even on printing terminals. Edlin wasn't at all bad. The one line editor I could never get my head around was CP/M ED.COM. One day, back when I was young and my mind fairly nimble, I sat down and figured, "SOMEONE thought this was a good idea", and figured I'd force myself to learn it. It's worked for me with a lot of things in the past. Well, after almost an entire day, I got a one page assembly program entered in (just copying a printed example...copy/paste was still years away), and if I recall properly, compiling correctly. And I still couldn't comprehend CP/M ED.COM. Never met someone who said, "Hey, I'm good with CP/M ED", either. Don't even recall ever meeting anyone who said, "I can use ED".
And no -- no relationship to the Unix "ed" command.
I used it back in the day, on a machine name I forget (had a W in it, as I recall). School had rooms of these things - green screen, with their own diskette standard (nice captive market there for the school shop).
All I actually remember using it for was occasional small bits of homework (I seem to recall there being a more full-featured WP thingy for serious work) and writing up stuff to do with WH40K.
I grew up on TECO. I was happy to move to a screen-based editor once they were common, but I do think that background makes me a bit more accepting of line-based one, even though they're mostly crap compared with TECO.
I don't recall the commands for edlin now. But MS-DOS's general model was to take some tool built for Unix or RSX-11, dumb it down until it was nearly, but not completely unusable, change some things (like the directory separator character) so your muscle-memory constantly misled you, and then make it essential.
I think that the world has missed a trick. Borland back in the 1980s and early 1990s has some fantastic TUIs, and they were really, really good. All of that got thrown out with the arrival of the GUI, and now we’ve successfully screwed things up to the extent where it’s now hard to have a GUI app remotes to a terminal (like we could with X applications), people are reinventing TUI apps for use in SSH shells. It really is quite pathetic.
Quattro Pro was a masterpiece of a TUI.
I bash ms at most opportunities through I have to admit edit.com served very well. Column, row indicators and a simple but not obscure UI. A far cry from what they produce today. I never really got on with amiga Memacs, on the extras 1.3 disk. 30 years on various Emacs flavours still dont float my boat. There was one that used to ship with Mandrake Linux I quite liked. Vi and edlin were and are masochistic for anything beyond a one line edit. Nano is somewhere in between. Expanding on the UI turns it into something else so I don't half wonder if v5 should be a fork!