I almost feel like this a somewhat pointless feature. It’s almost easier to just learn the default ones as opposed to adding “-modernbindings” or creating an “enano” variant/copy.
Wait, people are still using nano?
People who only use the terminal to edit a few config files are usually fine with nano. Even more so with these new keybindings.
For more involved edits an editor like VSCode is usually more useful anyway.
For me vim works well, but I’ve already taken the time to learn its basic usage.
What does “modern” mean? Emacs-like? Vim-like? Some other bastard system?
So “some other bastard system” it is, then.
That’s a shame; a GNU project should be consistently GNU-like (i.e. adopt Emacs key bindings).
There’s already Emacs, Vim, Kakoune, etc for that. Nano is supposed to be the system default for non-advanced users.
After all that, no ^S to save 🥲
True, I remember the first time I used nano, I was like “Ctrl + O to save, huh?”
^S works!! …As revealed by our kind palindromic friend on the other sibling comment! Why they don’t just list it on the statusbar we would never know!
Probably because Ctrl+S is the shortcut for scroll lock on the terminal so it can be a bit problematic if you start using it when not in nano. It freezes the output and you have to use Ctrl+Q to unlock.
^S for unprompted save is in the default keybinds, not that I could say when it was added. (Pretty sure it wasn’t a pico thing, but that leaves quite a bit of time unaccounted for.)
Muscle memory for other editors kicked in when I was editing something and did a literal slow realisation and double-take when it worked.
Now if only I could stop pressing ^W in Firefox to use nano’s “whereis” to find something that’d be great.
For those unaware, it closes the current tab. Or the whole browser. Ugh.
True. Other tools include: Ctrl+Shift+N to bring back a closed window if there’s another window of the same browser instance still open, and when there isn’t, there’s Restore Previous Session which is accessible a couple of ways.
Neither bring back the comment that was being typed in a textbox on the page though. Guess when I usually ^W
That’s your opinion.
I like updating it to modern conventions. One day they become default and on another day you get rid of the old ones. The people of the future don’t have to learn two sets of keybindings.
It’s definitely just my opinion. Honestly did not mean to imply otherwise.
I would almost prefer them to just switch to the new keybindings by default in version 8.0.
It’s definitely just my opinion. Honestly did not mean to imply otherwise.
For my opinion I usually create a comment below my post to seperate my opinion and the post itself.
On-topic: I do believe it’s useful to have this switch and there’s nothing stopping distros to change their default. Completely replacing the default keybindings might be surprising to long time users, but I also believe it should be done at some point. For the meantime this switch can be simply added as an alias.
Fair point. I guess this was more of a casual post, so I didn’t think too much about it.
I would have preferred if they switched to new keyboard model in version 8.x by default.
I am a relatively light Linux user. Raspberry Pi headless via DietPi/Debian for NAS/Media server/torrents/PiHole and some experiments with self hosted services on major cloud services. I prefer to stick to defaults whenever possible.
