GNU nano is a nice easy text editor… but it’s so clunky when you have become comfortable with vim (perhaps the same with Emacs).
The trick is to never get comfortable with Vim or Emacs.
*taps forehead*
Using nano as a vim user is a lot less clunky than trying to use vim as a vim non-user though.
Or so I would imagine, all of the vim novices are still too busy trying to exit vim to share their experiences.
The worst and best thing you can do when using vim is learn the movement keys (
h,j,k, andl) because they’re so powerful and work no where else.There is a vim mode available in a lot of other applications though.
handlare overrated, usew,b,eandfinstead.Yeah, doesn’t work so well when you’re not using qwerty though
That’s not true. I’m on qwertz and I adore vim key bindings
Okay, perhaps I should have been clearer, that’s on me.
I meant qwerty and related layouts.
Things like Dvorak and Colemak, the movement keys are spread across the keyboard and if you want to navigate that way you’ll pretty much have to remap them, and probably remap the keys you’ve swapped. For me, it’s just easier to use the arrows than go through that.
I mean, yeah, of course. Vims default keys are made for the “regular” layouts. But you can Mal everything yourself if needed. I’m sure there are pre made mappings for other layouts too.
I might check that out
Using the arrows may not be the most efficient, but I’m not spending enough time in vim to make that be an issue… Though I’ve seriously considered trying to swap to it from VSCode
Annoys me that “modern” in this case means whatever Microsoft does and whatever Microsoft users are used to. Especially since a lot of those “modern” binding have been around since the 80s.
“Modern” has become one of those words that’s way over used to the point of meaninglessness.
Those keybindings are prevalent outside of windows though, Ctrl+C is almost universally copy and Ctrl+V is almost universally paste - it might have been popularised by windows at some point in history but it’s well beyond that.
There’s an argument for consistency, especially with basic functions.
Lol I wasn’t aware that nano is actually a GNU project. Checking the date on Wikipedia when it became one really threw me off today morning: 2001. Man I was living behind the moon and could not exit properly the entire time!
I remember using Pico, Nano’s predecessor, in the mid-to-late '90s. Nano was created because there was a desire to distribute Pico with Linux. Unfortunately, the licensing was unclear so a clone had to be made. Fortunately there was no argument about editor appearance and behaviour.
As shocking as the 2001 date might be, it seems like Pico might have ceased development as recently as the end of 2022 along with its e-mail reader parent program Alpine (formerly Pine).
If true, Nano still has a few years to go before it will overtake its parent for longevity.
(Both vi and Emacs are far older, of course.)
vim > all
