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.
You must log in or register to comment.
Wait, people are still using nano?
Yes
I started with vi, and I still prefer to use nano.
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.
After all that, no
^Sto save 🥲True, I remember the first time I used nano, I was like “Ctrl + O to save, huh?”
^Sworks!! …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.
^Sfor unprompted save is in the default keybinds, not that I could say when it was added. (Pretty sure it wasn’t apicothing, 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
^Win Firefox to usenano’s “whereis” to find something that’d be great.For those unaware, it closes the current tab. Or the whole browser. Ugh.
:GASP:
^Sdoes save! I have played myself for a fool all these years!!Now I just have to unlearn
^X, Y, enter. . . :thisisfine:Firefox desperately needs a way to customize keyboard shortcuts, especially to disable them. Shortkeys isn’t really enough.
What does “modern” mean? Emacs-like? Vim-like? Some other bastard system?
Read the Article. Modern like what most Graphical Editors Ship.
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.
There are now 15 standards
There are now 15 standards
No, there is and always has been just the one standard text editor.
If Emacs keybindings are good enough to be the system default for Mac users, they should be good enough for anybody.
That’s a subjective take. GNU Nano has always been the default editor for so long alongside vi. But when you say that Emacs keybindings are good for Mac user - I can’t help but wonder - what type of generalization is that? Do you have a source to back this claim?
Now, don’t get me wrong - I love Kakoune. But no one outside of the developer community will make an effort to learn atypical text editors with chords and modes.
Given that Mac keybindings for “common special functions” (Open/Save/Cut/Copy/Paste/Find/etc.) use Command instead of Ctrl, leaving Ctrl effectively unused unless in combination with Command, this argument doesn’t hold much water.
Sure, some Emacs fan at Apple decided to add Emacs shortcuts to Cocoa controls, but that was a pretty arbitrary decision since people coming from Mac OS 9 didn’t use the Ctrl key, well, ever.
