Originally posted by waxhead
View Post
Announcement
Collapse
No announcement yet.
Nano 8.0 Text Editor Released With Modern Bindings Option
Collapse
X
-
Originally posted by npwx View PostI don't quite get why some distributions set this as a default editor. Just recently I noticed one of my Fedora systems opening up nano as $EDITOR. The system itself is huge, the reason can not possibly be <0.1% of disk space savings?
Yes, I know the vi/emacs crowd is out there, but they know how to install their tools anyway.
Last edited by S.Pam; 01 May 2024, 02:30 PM.
- Likes 15
Comment
-
Originally posted by nadir View Post
It's justabout what you learned. There is nothing intuitive about nano if you're somebody used to vim keybindings.
Navigating around with arrow keys and entering weird key combos to quit/save is how I experience it whenever I'm thrown into it. Very similar feeling to how somebody unfamiliar with vim bindings describes it when they get thrown into vim.
I'm using the commandline for a lot of my daily tasks and Nano feels weird to me.
- Likes 14
Comment
-
-
So to use the modern keybindings you have to run it with the --modernbindings option which users not going to bother to do, especially newcomers. They should just use the modern keybindings by default.
Also what's this that nano has to be compiled with --enable-utf8 option, that is stupid, it is 2024, they should remove that compile-time option and always compile with UTF-8 support.
- Likes 5
Comment
-
Micro is just a better editor in every single way, including "normal" bindings, other than install size. And it's still only 12.5 MB on disk. I don't understand how nano is still the default editor other than the fact that it's a GNU project. I highly recommend anybody needing a simple TUI editor that isn't Vim to check it out. I've even modified my windows install to use it instead of Notepad.
- Likes 2
Comment
-
If you are/were a user of the Pine/Alpine mail client the old nano key bindings are likely familiar. Nano was a GPL rewrite of the editor Pico which was covered by Washington Uni's licensing at the time.
Personally I configured Pine to invoke vi for composition but Pico was the goto editor on Unix boxes for users from msdos/macos/windows environments.
I reckoned that they would find emacs or vi without my assistance (or not.)
Back then knowing /bin/ed was much more useful as that was normally all you had when you were dumped into single user on booting - usually a stuffed up config file.
Michael J Lucas' Ed Mastery is highly recommended for those not having had that pleasure.
He even has the misogynist's Manly McManface version - it costs more but you expect to pay more for (ine)quality.
Comment
Comment