The problem I had with nano is that, for the time being, it was supposed to be easy to use. With that in account I always get lost when saving a file and closing the thing because one’s used to doing something else with Ctrl+O and Ctrl+X.
Whereas with Vim (and Neovim for a little while, and now with Vis) I knew it had a steep learning curve from the start so I always had it in mind. And all the funny stories about quitting vim.
The problem with using nano for years is that I now try using nano shortcuts in other programs. Random new windows opening is confusing, until you figure out Ctrl+o isn’t save in that program. Then it’s just annoying because you still have your inappropriate muscle memory.
The problem I had with nano is that, for the time being, it was supposed to be easy to use. With that in account I always get lost when saving a file and closing the thing because one’s used to doing something else with Ctrl+O and Ctrl+X.
Whereas with Vim (and Neovim for a little while, and now with Vis) I knew it had a steep learning curve from the start so I always had it in mind. And all the funny stories about quitting vim.
they’ve changed those bindings now, Ctrl+S, Ctrl+X, Ctrl+V, and Ctrl+C all do what you think they do
Great, now the next time I use nano I surely will forget about this and get frustrated when trying to save a file with Ctrl+O
you still can, but I think Ubuntu and other prepacked distros will switch soon to the better bindings
Great so now I will mangle all my merge commits depending on which version the host is using.
I’m thinking Ctrl+C quits and Ctrl+S is scroll lock is that correct?
nanonano --modernbindingsI mean quitting vim isn’t hard you just reset the computer.
The problem with using nano for years is that I now try using nano shortcuts in other programs. Random new windows opening is confusing, until you figure out Ctrl+o isn’t save in that program. Then it’s just annoying because you still have your inappropriate muscle memory.