81–90 of 154 posts
Nano can get partially there, micro is the current best though it has a few MacOS oddities around home/end but can be configured, in the past used ne.
I'm sure nano/pico and the like are nice but to me there's two things a terminal editor can try to solve for: being nice, or bring ubiquitous. The nicest ones (say emacs) are way nicer than nano in terms of features, extensibility, etc. Now for being ubiquitous, nothing beats vi to date. I can't tell what nano is aiming for? EDIT I guess I had assumed that vi/vim was significantly more widespread than nano. Maybe tha…
Why nano? nano is sane. With Emacs/VI you need to bring a HUGE mental framework to just use it. And maybe, with luck or some years of pain training, to just EXIT it :) --- Vim/emacs are powerful. Nice? Never. Easy? never. Good for most common editing task in the terminal?. Nope. Claim that Vim/Emacs are good is like say "why people use Sublime Text when Eclipse is so much better?" Except, with eclipse, you know how e…
"nano" is an interesting creature - it was originally developed as a replacement for the "pico" command that shipped with "pine" (an amazing curses-based email client) because the license on pico was just not really clear. I still use nano 50% of the time because it's so easy to jump into a file, make some quick changes, and jump out. Plus the mark/cut/paste keystrokes are seared into my memory after years of use.
I would recommend micro. It's simple like nano, but has full mouse support. The only real downside is that it's not installes by default.
This is why I recommend to anyone wanting to try a -nix like OS to learn the basic commands in both vi and nano. One or the other is shipped with every -nix like OS I've ever used. Once they get more used to the OS, go ahead and install whatever editor they want to. But logging into a fresh install of pretty much any system, one can get by with either of the two.
Earlier quoted context omitted.
I'm confused. The only reason one uses nano is because you ssh'ed into some random machine and you are stuck with whatever is on it. If you got enough bother to install micro or fiddling with the settings of nano you might as well setup something more proper.
I'm a GUI dev/UX/education designer. Nano/pico to me are the only cli editors remotely suitable for ordinary human cognition. I have faint interest in the Emacs ecosystem, but wish it took basic ergonomics into account more seriously. I do understand I could get used to the lack of affordances but life's too short, perhaps. I understand keyboard usage wins you speed but not sure it's worth the general unpleasantness.…
Earlier quoted context omitted.
So one day someone will write the improvement and call it milli, but then what? Is there a prefix for 10^0? Do these people not plan ahead?
Well you can use some of the convenience steps around 1, e.g. centi and deci and then skip the 1.0 and go straight to deca and hecto.
Serious question: how often do you log into a box where it would be impossible or considered rude for you to install a proper editor? I feel like I must have been blessed by the sysadmins in my life (them often being me) but it's never happened in 25 years of logging into *nix boxes.
>An overlong line is no longer automatically hard-wrapped. Finally. It was one of the most insane defaults in the history of text editors. Things like this are the reason why it's so hard to recommend nano to beginners.
I like the idea of hard wrap, line of code shouldn't be longer than 80 characters... sure it's confusing for beginners + sometimes data shouldn't be hard-wrapped, but in general (imho) it's better than worse
Earlier quoted context omitted.
Because if I type "hello" in a document, I expect the editor to save "hello", not "hello\n".
Where did you get that expectation? Every editor I've used up until Visual Studio Code did that by default. (I was actually very surprised when vscode _didn't_ do this!)
Earlier quoted context omitted.
sane is what the user expects, not what POSIX demands.
One could reasonably expect that a user expects a POSIX system to behave according to the POSIX standards?
It's too bad the Windows Store only contains Ubuntu LTS editions. It'll be July 2020 before all the improvements from 2.9.3 on up become available for most WSL users. :(
It’s really as trivial to dist-upgrade Ubuntu on WSL as real Ubuntu.
Heck, I bet 19.04 works fine already if you dare run a beta.